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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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
  • #6010

Closed (moved)
Open
Opened May 31, 2012 by Nick Mathewson@nickm🐭

UpdateBridgesFromAuthority isn't actually usable

Thanks to the bug #1938 (moved) fix, UpdateBridgesFromAuthority only works if you can build a circuit to the authority. But if you're using bridges, you can't connect to the authority without bridges, so setting UpdateBridgesFromAuthority 1 is still not going to be a great idea unless you already have a bridge descriptor somehow.

What we should really do (according to comments on #1938 (moved) , which I agree with) is implement behavior where we can try the authority or try asking the bridges we know, falling back from one to the other intelligently.

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