[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #11512 [Tor Launcher]: Tor Launcher should set ClientTransportPlugin according to the bridge list

#11512: Tor Launcher should set ClientTransportPlugin according to the bridge list
------------------------------+-------------------
     Reporter:  anonym        |      Owner:  brade
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:
    Component:  Tor Launcher  |    Version:
   Resolution:                |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |
------------------------------+-------------------

Comment (by mcs):

 Kathy Brade and I did some evaluation of this issue.  We would prefer to
 have Tor Launcher know as little as possible about the
 ClientTransportPlugin configuration, especially since this issue should
 disappear when #8402 is completed.

 Our proposal is to store the ClientTransportPlugin values as hidden
 preferences, like so:
 {{{
 pref("extensions.torlauncher.transport_plugin.fte",
   "fte exec ${TORPATH}/PluggableTransports/fteproxy --managed");
 pref("extensions.torlauncher.transport_plugin.obfs2,obfs3",
   "obfs2,obfs3 exec ${TORPATH}/PluggableTransports/obfsproxy.bin
 managed");
 pref("extensions.torlauncher.transport_plugin.flashproxy",
   "flashproxy exec ${TORPATH}/PluggableTransports/flashproxy-client
 --register :0 :9000");
 }}}

 Tor Launcher would simply replace ${TORPATH} and use the resulting string
 for the SETCONF ClientTransportPlugin commands.

 Also, we can avoid the IPv6 issue if we assume that the first token in the
 bridge configuration may be a transport type; if it happens to be an IPv4
 or IPv6 address, it won't match any known types so it will be ignored.
 The only downside we see for this simple approach is that Tor Launcher
 will not be able to display a warning for unknown types.  A slightly
 smarter approach might be to check that the first token consists entirely
 of 0-9, A-F, ":" and "." (in which case it should be an IPv4 or IPv6
 address with optional :port and not a transport type).

 For the UI, we will need to think more about how to handle the fact that
 the proxy and bridge options are mutually exclusive.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11512#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs