Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #10229

Closed (moved)
(moved)
Open
Created Nov 24, 2013 by Trac@tracbot

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

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.

Trac:
Username: ConcernedUser3Ir5

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking