Opened 2 years ago

Last modified 2 years ago

#21892 new defect

ControlSockets are not created if tor starts with DisableNetwork set

Reported by: anonym Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.9.10
Severity: Normal Keywords: AffectsTails
Cc: mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by anonym)

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 TCP listeners work as expected vs DisableNetwork, AFAICT.

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

Child Tickets

Change History (3)

comment:1 Changed 2 years ago by anonym

Description: modified (diff)

comment:2 Changed 2 years ago by mcs

Cc: mcs added

comment:3 Changed 2 years ago by dgoulet

Milestone: Tor: unspecified

Missing milestone.

Note: See TracTickets for help on using tickets.