Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #21892

Closed (moved)
Open
Opened Apr 07, 2017 by anonym@anonym

ControlSockets are not created if tor starts with DisableNetwork set

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.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#21892