Skip to content

GitLab

  • Menu
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 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • #4392
Closed
Open
Created Nov 05, 2011 by Sebastian Hahn@sebastian

UpdateBridgesFromAuthority is problematic

When UpdateBridgesFromAuthority is set to 1, Tor makes a direct connection to Tonga to fetch the bridge descriptor referenced in the configuration, as long as it includes the fingerprint. This happens before even trying the bridge directly, so we definitely leak to censors that a) we're a tor client, trying to use bridges; and b) that we'll soon connect to a real bridge IP:port. Back when Tonga wasn't blocked, this seemed fine, but now that we have adversaries that actually pick up on the Tor handshake or network behavior and send active probes, this seems like a poor idea.

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