[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 anonym):
Replying to [comment:9 mcs]:
> Replying to [comment:8 anonym]:
> > Has there been any progress on this?
>
> As of TBB 3.6.2, a local HTTP or SOCKS proxy can be configured for all
included Pluggable Transports. The presence of ClientTransportPlugin
config statements should not affect regular use of proxies either. If
Tails can incorporate (or has incorporated) the PT and tor fixes that are
included in TBB 3.6.2, it should no longer be necessary to modify Tor
Launcher. If you agree, we can close this bug.
I see. You have backported the (current) fix for #8402 into the Tor you
ship in TBB 3.6.2. I doubt we want to carry this delta in Tails since we
prefer to ship the unmodified, stable Tor versions built by the Tor
Project, both to benefit from their QA process, and to ease our
maintenance burden.
Since you have this fix in Tor I understand that any a fix in Tor Launcher
(as proposed before) does not make sense for you any more. I suppose we
just continue to modify our Tor Launcher in Tails until Tor 0.2.6.x goes
stable.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11512#comment:10>
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