Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Arti Arti
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 138
    • Issues 138
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • ArtiArti
  • Issues
  • #438
Closed
Open
Created Apr 08, 2022 by Nick Mathewson@nickm🎨Owner

Cached directory object from the future makes us fail bootstrapping; is this right?

Our current behavior, when starting with a consensus from the future, is to fail to bootstrap, and exit the bootstrap function with an error: since the consensus is from the future and validated, our time is necessarily in the past, and bootstrapping cannot succeed.

Several things to do here:

  • Make the error message better.
  • Make sure that we only do this for a consensus that we have authenticated as well-signed by the authorities we believe in.
  • Think about whether this is truly what we want.
Assignee
Assign to
Time tracking