[tor-bugs] #21892 [Core Tor/Tor]: ControlSockets are not created if tor starts with DisableNetwork set

[Tor Bug Tracker & Wiki]

#21892: ControlSockets are not created if tor starts with DisableNetwork set
------------------------------+---------------------------
     Reporter:  anonym        |      Owner:
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:
    Component:  Core Tor/Tor  |    Version:  Tor: 0.2.9.10
     Severity:  Normal        |   Keywords:  AffectsTails
Actual Points:                |  Parent ID:
       Points:                |   Reviewer:
      Sponsor:                |
------------------------------+---------------------------
 The summary says it all basically, but note that if `tor` was started with
 `DisableNetwork 0` in `torrc` so the control socket is opened, and then we
 set `DisableNetwork 1` (in `torrc` + send a `SIGHUP`), then the control
 socket is *not* closed. So there's also some inconsistency with this
 option being set at start vs setting it after start, which might help
 debugging this.

 And just to be clear: `ControlPort` listeners work as expected vs
 `DisableNetwork`, AFAICT.

 FWIW, this affets the default `torrc` (+ the default `torrc` of course) in
 Debian with `DisableNetwork 1` added.

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