ControlListenAddress ip:port vs. ControlPort settings
When configuring Tor's control port, there are currently two ways to do this:
-
Just configure "ControlPort 9051" and have Tor listen on 127.0.0.1:9051 for control connections
-
Configure "ControlListenAddress 10.0.0.1:8051" and have Tor listen on 10.0.0.1:8051. Note that this also requires ControlPort to be configured, but not necessariliy for port 8051.
Approach 2) seems counter-intuitive. If I want Tor to listen for control connections via ControlListenAddress, it should be possible to do so by simply using the ControlListenAddress option and not require the ControlPort option to be set, too. The user will be confused if she configures ip:port and Tor then asks for a ControlPort to be present. If Tor needs ControlPort for some reason, it should read the port value of the ip:port combination used. If thats not possible, maybe the :port part of ControlListenAddress option should go.