Skip to content
GitLab
Projects Groups 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
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #27735
Closed (moved) (moved)
Open
Issue created Sep 17, 2018 by teor@teor

Tors with cached consensuses can't upgrade to a version that stops supporting a required protocol

When Tor loads the cached consensus, it checks the protocols in that consensus, and then exits if it does not have any required protocols. These checks happen before signatures and expiry are checked. (And before trying to get a new consensus.)

This makes it impossible for a Tor with a cached consensus to stop supporting a protocol required in that consensus.

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