Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #7066

Closed (moved)
(moved)
Open
Created 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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking