Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #6010
Closed
Open
Issue created May 31, 2012 by Nick Mathewson@nickm🌻Owner

UpdateBridgesFromAuthority isn't actually usable

Thanks to the bug #1938 (closed) 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 (closed) , 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.

Edited Nov 19, 2021 by Cecylia Bocovich
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking