Re: [tor-bugs] #18113 [Applications/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_information
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-bridges|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor30-can
---+---
Changes (by pili):

 * sponsor:   => Sponsor30-can


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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_information
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-bridges|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by mcs):

 * status:  needs_revision => needs_information
 * cc: nickm (added)


Comment:

 I am triaging old tickets.
 Tor Launcher still randomly reorders the bridges each time it starts up.
 But maybe it shouldn't because tor is doing something smart now? Nick?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-bridges|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by brade):

 * keywords:  tbb-bridges, TorBrowserTeam201604 => tbb-bridges


Comment:

 removing outdated keyword

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-bridges, TorBrowserTeam201604  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by arma):

 Replying to [comment:19 arma]:
 > 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.

 I opened #19875 for this idea.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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:
 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 isis):

 Replying to [comment:19 arma]:
 > (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.)

 So you mean we would add a parameter to bridge lines that specifies
 weight? Or another optional line underneath it like

 {{{
 Bridge 1.2.3.4: 0123456789abcdef0123456789abcdef01234567
 BridgeWeight 8
 Bridge 5.6.7.8:4545 f0123456789abcdef0123456789abcdef0123456
 BridgeWeight 2
 }}}

 Changing the bridge lines once we're taking PTs into account starts to get
 super ugly… I think if we're going this route we'd need to add something
 like the BridgeWeight lines.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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:
 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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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:
 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 gk):

 Replying to [comment:17 isis]:
 > Replying to [comment:8 gk]:
 > > Ok, I'll take the patch as is as we are running out of time and it is
 improving the situation I think. That said I am a fan of the persisting
 option + bringing the available bridge bandwidth into the equation. We
 know the operators and could ask them + hardcode the bandwidth using that
 value for distributing users even more fairly. These (and other)
 enhancements should be done in a follow-up ticket though.
 >
 > Should we close this ticket and make new tickets for persisting the
 ordering and another for hardcoding the bandwidth?  Is there any revision
 of my patch that still needs to be done?

 See: comment:6. I think at least item 1) and 3) are worth it. And, yes,
 for persisting the ordering and bandwidth hardcoding we should make
 separate tickets.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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:
 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 isis):

 Replying to [comment:8 gk]:
 > Ok, I'll take the patch as is as we are running out of time and it is
 improving the situation I think. That said I am a fan of the persisting
 option + bringing the available bridge bandwidth into the equation. We
 know the operators and could ask them + hardcode the bandwidth using that
 value for distributing users even more fairly. These (and other)
 enhancements should be done in a follow-up ticket though.

 Should we close this ticket and make new tickets for persisting the
 ordering and another for hardcoding the bandwidth?  Is there any revision
 of my patch that still needs to be done?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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:
 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 isis):

 Replying to [comment:15 mrphs]:
 > Replying to [comment:11 teor]:
 >
 > > I'm not sure what you mean here, surely there can only be one "first"
 bridge each time Tor Browser launches.
 >
 > If you take a look at `bridge_prefs.js` file, the first obfs4 bridge
 starts with:
 >
 > {{{
 > pref("extensions.torlauncher.default_bridge.obfs4.1", "obfs4...
 > }}}
 > and the second one with
 >
 > {{{
 > pref("extensions.torlauncher.default_bridge.obfs4.2", "obfs4...
 > }}}
 > What happens if they all are `obfs4.1`? Does Tor Browser try to connect
 to all of them at once?

 If they are all `pref("extensions.torlauncher.default_bridge.obfs4.1",
 "obfs4...` then the pref is overwritten each time, and you'd only end up
 with one bridge, because FF prefs are key-values which expect keys to not
 collide.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18113 [Applications/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:
 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 mrphs):

 Replying to [comment:11 teor]:

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

 If you take a look at `bridge_prefs.js` file, the first obfs4 bridge
 starts with:

 {{{
 pref("extensions.torlauncher.default_bridge.obfs4.1", "obfs4...
 }}}
 and the second one with

 {{{
 pref("extensions.torlauncher.default_bridge.obfs4.2", "obfs4...
 }}}
 What happens if they all are `obfs4.1`? Does Tor Browser try to connect to
 all of them at once?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs