Skip to content
GitLab
Projects Groups Topics 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
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #24740
Closed (moved) (moved)
Open
Issue created Dec 25, 2017 by teor@teor

Tor launches two requests for authority certificates on first bootstrap

When tor first bootstraps, it launches two requests for authority certificates:

  • one is the hinted request that goes to the directory it downloaded the consensus from (ticket?)
  • one is a scheduled request that goes to a random directory

We should delay the first scheduled request slightly (5s?) to allow the first request to complete. This might be as easy as changing the first number in the authority certificate schedule from 0 to 5.

I thought we avoided fetching certificates if another fetch was in progress: clearly that doesn't happen, and maybe we don't want it to, because we don't want to wait a whole 10 seconds for it to timeout.

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