Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 832
    • Issues 832
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #12688

Closed
Open
Created Jul 23, 2014 by Roger Dingledine@armaReporter

Make NumEntryGuards configurable by the consensus

I plan to move clients to using 1 guard rather than 3. But I'd like to do that in a way that we can move them over as a group, once enough people have upgraded. I think that calls for a consensus param.

I shall call it NumEntryGuards.

And the controversial point is that I want to put it into 0.2.4.x as a security fix.

The timeline will be for some folks to upgrade, then we stick it in the consensus as NumEntryGuards=1, then when nothing explodes, we change the default-if-it's-not-in-the-consensus to 1, and eventually we don't need to set the consensus param anymore.

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