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

Closed (moved)
Open
Opened May 22, 2012 by Aaron Gibson@aagbsn

BridgeDB should respond with the same address:port to each request

When a Bridge has multiple listening addresses/ports, a valid bridge line is selected and returned to the client. No effort is made to make sure that the same address:port is returned for each request. This is a design flaw, as a single client could expose all listening addresses and ports of a given bridge.

BridgeDB should respond with the same address:port per bridge for repeat requests.

This can be implemented in a pretty straightforward way, by mapping the requesting {ip, email} to one of the address lines and one valid port.

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#5948