#18113: Dynamically allocate clients to default Tor Browser bridges of a certain
type
-----------------------------------------------+---------------------------
Reporter: isis | Owner: brade
Type: enhancement | Status:
Priority: Medium | needs_revision
Component: Applications/Tor Launcher | Milestone:
Severity: Normal | Version:
Keywords: tbb-bridges, TorBrowserTeam201604 | Resolution:
Parent ID: | Actual Points:
Reviewer: | Points:
| Sponsor:
-----------------------------------------------+---------------------------
Comment (by arma):
Ok, this ticket came a long way since I last noticed it.
I agree with what Yawning said way up at the top -- this is best fixed
inside Tor.
Tor already has the mechanism for figuring out which bridges work, and
also the mechanism for keeping state about which one it picked to be its
"first" bridge (they go into the state file and are treated just like
guards).
So all Tor needs to do is shuffle its bridge list every time it reads it
from torrc, and I think everything else we need will follow.
(Except the bandwidth weighting stuff -- either Tor chooses from all of
them equally because it doesn't have any descriptors at the time it
chooses which one will go into the state file first, or it does have the
descriptors so it weights by the self-advertised bandwidths in the
descriptors. I'd have to check, but my guess would be the former. Still, I
think that is better solved inside Tor, where Tor Browser's job would be
to add a weight to the bridge line.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18113#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
