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

Closed (moved)
Open
Opened Sep 01, 2011 by cypherpunks@cypherpunks

Controlport behavior changed in 0.2.2.32 - CookieAuthentication now required to access control port

Current and previous versions of the torrc file states that either a HashedControlPassword OR CookieAuthentication may be used to access tor's controlport.

From torrc

If you enable the controlport, be sure to enable one of these

authentication methods, to prevent attackers from accessing it.

#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C #CookieAuthentication 1

After upgrading from 0.2.1.26 to 0.2.2.32, tor now requires that CookieAuthentication be enabled to access the ControlPort. Upon starting Vidalia after the tor upgrade, an error message was received asking for the location of the authentication cookie even when a HashControlPassword was specified in the torrc file.

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