Opened 7 years ago

Closed 7 years ago

#10229 closed enhancement (worksforme)

feature req: Runtime reconfigure Tor daemon to listen on additional addresses

Reported by: ConcernedUser3Ir5 Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


It might be useful for the Tor daemon to expose a way to add and remove "ORPort" records at run-time, without restarting the daemon. For example, consider a Tor host on a multi-homed NATted network, where each public address is usually stable but cold change from time to time, and not necessarily when the host is rebooted. Or, consider a Teredo address for the host, or some other IPv6 tunnel, which is randomly assigned at boot and may require an additional script to start/stop. It would be possible to have the start script for the Tor daemon rewrite /etc/torrc/ with such additional addresses, but that mixes "dynamic" configuration with "static". Or, those additional addresses could have DNS names, but dynamic DNS is harder to set up for such additional addresses.

This could be an optional additional (TCP) control socket, or a control option built into the protocol itself (probably a bad idea, potential security hole if not properly implemented), or a Unix-domain control socket that only accepts connections from "root" or other allowed daemons.

Child Tickets

Change History (2)

comment:1 Changed 7 years ago by arma

You're in luck! Check out the control protocol (and setconf in particular).

comment:2 Changed 7 years ago by nickm

Resolution: worksforme
Status: newclosed

Also, if you're on a unix-like system, you can just edit the torrc file and send Tor a SIGHUP. That's not as flexible as the full controller protocol, but it's quite a bit easier.

Note: See TracTickets for help on using tickets.