[tor-bugs] #25173 [Core Tor/Tor]: No Control Socket when DisableNetwork and User options are set

[Tor Bug Tracker & Wiki]

#25173: No Control Socket when DisableNetwork and User options are set
--------------------------+------------------------------------
 Reporter:  iry           |          Owner:  (none)
     Type:  defect        |         Status:  needs_information
 Priority:  Medium        |      Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.1.9
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by arma):

 Our first weird hint. Not using the User option, we have
 {{{
 Feb 07 22:06:02.093 [notice] Read configuration file
 "/usr/local/etc/tor/torrc".
 Feb 07 22:06:02.098 [warn] ControlPort is open, but no authentication
 method has been configured.  This means that any program on your computer
 can reconfigure your Tor.  That's bad!  You should upgrade your Tor
 controller as soon as possible.
 Feb 07 22:06:02.098 [notice] Scheduler type KIST has been enabled.
 Feb 07 22:06:02.098 [notice] Opening Socks listener on 127.0.0.1:9050
 Feb 07 22:06:02.098 [notice] Opening Control listener on 127.0.0.1:9051
 Feb 07 22:06:02.098 [notice] Opening Control listener on
 /home/arma/.tor/control
 Feb 07 22:06:02.098 [notice] Opening Control listener on
 /tmp/tor/control.sock
 Feb 07 22:06:02.098 [warn] Your log may contain sensitive information -
 you disabled SafeLogging, and you're logging more than "notice". Don't log
 unless it serves an important reason. Overwrite the log afterwards.
 Feb 07 22:06:02.103 [notice] Parsing GEOIP IPv4 file
 /usr/local/share/tor/geoip.
 Feb 07 22:06:02.220 [notice] Parsing GEOIP IPv6 file
 /usr/local/share/tor/geoip6.
 Feb 07 22:06:02.726 [notice] Bootstrapped 0%: Starting
 }}}

 That is, our controlsocket opens at the same time as the control port.

 But using User, we have
 {{{
 Feb 07 21:25:12.170 [notice] Read configuration file "/tmp/torrc".
 Feb 07 21:25:12.175 [notice] Scheduler type KIST has been enabled.
 Feb 07 21:25:12.175 [notice] Opening Socks listener on 127.0.0.1:9050
 Feb 07 21:25:12.000 [notice] Parsing GEOIP IPv4 file
 /usr/local/share/tor/geoip.
 Feb 07 21:25:12.000 [notice] Parsing GEOIP IPv6 file
 /usr/local/share/tor/geoip6.
 Feb 07 21:25:12.000 [notice] Bootstrapped 0%: Starting
 Feb 07 21:25:12.000 [notice] Starting with guard context "default"
 Feb 07 21:25:12.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network
 Feb 07 21:25:13.000 [notice] Opening Control listener on
 /tmp/tor/control.sock
 Feb 07 21:25:13.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop
 }}}

 What in our code path is making us open the control socket listener so
 much later when User is set?

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