[tor-bugs] #18113 [Tor Launcher]: Dynamically allocate clients to default Tor Browser bridges of a certain type

[Tor Bug Tracker & Wiki]

#18113: Dynamically allocate clients to default Tor Browser bridges of a certain
type
--------------------------+--------------------------------
 Reporter:  isis          |          Owner:  brade
     Type:  enhancement   |         Status:  needs_revision
 Priority:  Medium        |      Milestone:
Component:  Tor Launcher  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  tbb-bridges   |  Actual Points:
Parent ID:                |         Points:
  Sponsor:                |
--------------------------+--------------------------------

Comment (by teor):

 Replying to [comment:9 mrphs]:
 > To add to the complexity of this situation, I wonder what happens if we
 have for instance two bridges listed as the "first" bridge. Is there going
 to be an accidental load balancing in practice? or would it break things?

 I'm not sure what you mean here, surely there can only be one "first"
 bridge each time Tor Browser launches. (See below.)

 Replying to [comment:10 mrphs]:
 > Also, we have only 3 bridges on port 443 and only one on 80. how are we
 making it easier for censored people who only have access through this
 ports to pick the right one?

 As far as I understand it, this patch automatically reorders the default
 bridges used by Tor Browser each time it restarts. Then Tor Browser tries
 each bridge in turn to see if it works.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18113#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online