[tor-bugs] #1857 [Tor Client]: ControlListenAddress ip:port vs. ControlPort settings

[Tor Bug Tracker & Wiki]

#1857: ControlListenAddress ip:port vs. ControlPort settings
-------------------------+--------------------------------------------------
 Reporter:  kaner        |       Owner:               
     Type:  enhancement  |      Status:  new          
 Priority:  minor        |   Milestone:               
Component:  Tor Client   |     Version:  Tor: 0.2.1.26
 Keywords:               |      Parent:               
-------------------------+--------------------------------------------------

Comment(by arma):

 For background, this is the same way that ORPort / ORListenAddress works.
 In that case, the ORPort is what port you should put in your descriptor --
 that is, what you tell other people to use externally. What you bind to
 locally can be something different.

 We definitely shouldn't take away the :port part of ControlListenAddress.
 You can listen on more than one socket at once, and you specify that by
 multiple ControlListenAddress lines in your torrc.

 I wouldn't be opposed to a wrapper function listens_for_control_conns() or
 something that currently would just check options->ControlPort and in your
 new world would check either that or ControlListenAddress.

 We could also do something like that for the options->ORPort check.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1857#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online