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

Closed (moved)
Open
Opened Oct 07, 2012 by Robert Ransom@rransom

Guard disablement by path-bias detector must be disabled or removed

Currently, any three dirauths (or any two dirauths if one other one starts voting on the relevant consensus parameters) can configure Tor clients to stop using their entry guards after a very small number of failed circuit-build attempts. This is as bad for a client as having UseEntryGuards disabled entirely.

Tor 0.2.3.x users will be compromised by this without even a log message warning them that they are abandoning entry guards.

This feature must be disabled completely for now or removed. The current path-bias detector code is unsafe to use with any non-zero value of pb_disablepct.

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#7066