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 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • 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
  • #4187
Closed
Open
Created Oct 05, 2011 by anonym@anonym

A verified unverified-consensus should be renamed to cached-consensus

If Tor with a fresh $DATA_DIR gets a consensus and cannot verify, Tor writes it as $DATA_DIR/unverified-consensus. If Tor then is restarted and suddenly can verify unverified-consensus for whatever reason, Tor will start using it and never write a cached-consensus. While this doesn't cause Tor to misbehave AFAICT, the name of unverified-consensus is misleading since it in fact isn't unverified any longer.

Steps to reproduce:

  1. rm $DATA_DIR/*-consensus
  2. date --set="Jan 1 00:00:00 UTC 2013" # or whenever all current authority certs are expired
  3. start tor
  4. verify that Tor is not working and that you got $DATA_DIR/unverified-consensus
  5. stop tor
  6. set correct system time
  7. start tor
  8. verify that Tor is working and that there's no $DATA_DIR/cached-consensus, only $DATA_DIR/unverified-consensus
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking