Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #18605

Closed (moved)
Open
Opened Mar 21, 2016 by teor@teor

Consider including fallback directory mirrors with multiple IP addresses

arma describes the advantages of hard-coding bootstrap IP addresses that aren't in the consensus:

https://lists.torproject.org/pipermail/tor-dev/2016-March/010588.html

I think we could do this with fallback directory mirrors, to increase the chances of Tor bootstrapping successfully in these environments.

With two authority attempts in 0.2.7, it's roughly 47% (2/9 + 2/8).

We already have the same or greater probability of bootstrap success with fallbacks and authorities and an increased number of attempts. But it would be nice to use this trick for about 10% of fallbacks.

This will require changes to the fallback selection script and the whitelist format.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#18605