Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • U Utilities
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • Metrics
  • Utilities
  • Issues
  • #4250
Closed
Open
Issue created Oct 17, 2011 by Roger Dingledine@armaOwner

metrics consensus health should check the consensus from each authority

While doing a training yesterday, my poor os x user started tbb and it fetched a consensus that had two signatures on it -- one from gabelmoo-legacy, and one from moria1-legacy.

I didn't catch which authority gave it to her.

Several minutes later, Tor tried another authority and bootstrapped from there.

While we're checking network health, we should fetch a consensus from each authority and see if it is recent enough and has enough signatures on it.

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