Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #17372

Closed (moved)
(moved)
Open
Created Oct 18, 2015 by teor@teor

Use Guard as Fallback Directory

When a client hasn't used the Tor network for a few days, its consensus expires. If the authorities are blocked while it's offline, it can't bootstrap.

However, it has (almost) enough information to bootstrap from a semi-trusted relay - its guard.

This change requires:

  • a proposal
  • an additional line GuardFallbackDir in the state file, formatted like a FallbackDir line, if the guard is also a directory mirror

When #12538 (moved) is implemented, every relay (and therefore every Guard) will be a directory cache by default.

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