[tor-bugs] #10418 [Tor Launcher]: Make a "Use Default Bridges" Radio button in the Tor Launcher Bridge UI

[Tor Bug Tracker & Wiki]

#10418: Make a "Use Default Bridges" Radio button in the Tor Launcher Bridge UI
------------------------------+-------------------
     Reporter:  mikeperry     |      Owner:  brade
         Type:  enhancement   |     Status:  new
     Priority:  major         |  Milestone:
    Component:  Tor Launcher  |    Version:
   Resolution:                |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |
------------------------------+-------------------

Comment (by mcs):

 Kathy and I finished the work to select default bridges by type.  We also
 addressed various other loose ends.  The latest and greatest code is here:

 https://gitweb.torproject.org/user/brade/tor-
 launcher.git/shortlog/refs/heads/bug10418

 Preference values that should be pre-set / bundled:
 {{{
 extensions.torlauncher.default_bridge_recommended_type
 extensions.torlauncher.default_bridge.TYPE.#
 }}}

 The choice the user makes for transport type is stored in:
 {{{
 extensions.torlauncher.default_bridge_type
 }}}
 If that pref has a non-empty value, Tor Launcher uses default bridges,
 reconfiguring them each time TBB is started.  If the stored transport type
 does not match any of the available default bridges, Tor Launcher will
 display an error message and prompt the user to choose a different type
 (this situation could happen after an upgrade, and we did not want to
 silently go from using bridges to not using any bridges).

 Known issues:
 1) Tor Launcher does not do anything special to detect the situation where
 Tor is unable to successfully bootstrap using the bridges that are chosen.
 On the other hand, if this happens while the user is still in the initial
 setup wizard, they will be sitting on the bridge settings wizard panel
 when the error occurs... which is probably where we want them to be
 anyway.

 2) We did not really add any support in Tor Launcher for a pseudo-
 transport named "tor".  Maybe we should just wait until tor itself
 supports that... in the meantime, you can add a set of default bridges
 that appear to the user (in the dropdown menu) to use a transport named
 tor, e.g.,
 {{{
 pref("extensions.torlauncher.default_bridge.tor.1", "XXX.XXX.163.47:23");
 pref("extensions.torlauncher.default_bridge.tor.2", "XXX.XXX.213.48:23");
 }}}

 3) We do not add "(obfsproxy)" or other alternate names to the dropdown
 menu.  Tor Launcher just displays the TYPE from the
 extensions.torlauncher.default_bridge.TYPE.# preferences.

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