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

Closed (moved)
Open
Opened 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 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#4392