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
  • #4654

Closed (moved)
Open
Opened Dec 06, 2011 by cypherpunks@cypherpunks

Control TCP Socket not created under some circumstances

Hi!

I had to set ControlPort to get tor to open a control socket for TCP. Setting ControlListenAddress to e.g. 10.0.1.140:12345 does not suffice.

Additionally, I had to configure any kind of authentication method. The Documentation does not state, that authentication must be used to get a control socket. It actually says, that no authentication will be used unless it is configured explicitly.

I am using version v0.2.3.8-alpha with git commit id git-68475fc5c5a806eb.

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