Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • 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
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #25843

Make NumEntryGuards consistent with #271 consensus params

Right now, NumEntryGuards tries to do some magic to set "guard-n-primary-guards-to-use" to the torrc value, and "guard-n-primary-guards" to twice that value.

This prevents us from testing our current favored Proposal 291 params (2 for each). So the torrc option could either be changed to set both of those values to the same, or we could make two torrc options.

We should also ensure that whatever we do, we have the ability to set the torrc such that we could get the same behavior as all existing clients would get, with those consensus params, if we wanted. This includes directory guards (which we currently believe will and should be the same as the two primary guards).

asn has a testing branch here: https://github.com/asn-d6/tor/tree/prop291_testing. This is not ready for merge, be could be adapted into a mergable, backportable thing.

He also has a useful guard log promotion patch here: https://github.com/asn-d6/tor/tree/guard_monitor

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking