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

Re: [tor-bugs] #5018 [Tor]: don't start ClientTransportPlugin proxies until we have a bridge that wants them

#5018: don't start ClientTransportPlugin proxies until we have a bridge that wants
them
------------------------+-----------------------------------------
     Reporter:  arma    |      Owner:
         Type:  defect  |     Status:  reopened
     Priority:  normal  |  Milestone:  Tor: 0.2.4.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  pt tor-bridge, 024-backport
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-----------------------------------------
Changes (by mikeperry):

 * keywords:  pt tor-bridge => pt tor-bridge, 024-backport
 * status:  closed => reopened
 * resolution:  fixed =>
 * milestone:  Tor: 0.2.5.x-final => Tor: 0.2.4.x-final


Comment:

 For TBB 3.5, I want to be able to ship all of the pluggable transports
 with the default bundle so that users can enter PT bridge lines into Tor
 Launcher and have them work out of the box.

 However, I do not want the pluggable transport code to execute at all if
 users are not using pluggable transports. The most straightforward way to
 accomplish this for 0.2.4.x would be to backport this patch. Otherwise, we
 need custom configuration )and potentially restart) logic in Tor Launcher
 for 0.2.4.x but not 0.2.5.x, which is a situation I would like to avoid
 (and seems more risky than built-in Tor support for this behavior).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5018#comment:18>
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