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

Re: [tor-bugs] #11658 [Tor Launcher]: Unable to set the proxy in TBB 3.6 (was: Unable to set the SOCKS proxy in TBB 3.6)

#11658: Unable to set the proxy in TBB 3.6
------------------------------+-------------------
     Reporter:  sukhbir       |      Owner:  brade
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:
    Component:  Tor Launcher  |    Version:
   Resolution:                |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |
------------------------------+-------------------

Comment (by mttp):

 This applies not only to SOCKS proxies but HTTP proxies as well.


 Nick's IRC comments seem relevant:

 10:11 < nickm> GeKo: Does 3.6 provide a bunch of ClientTransportPlugin
 lines by                default, and rely on the backported #5018 fix to
 launch the right ones?
 10:11 -zwiebelbot:#tor-dev- [tor#5018: don't start ClientTransportPlugin
 proxies until we have a bridge that wants them]
 10:11 < GeKo> nickm: yes.
 10:11 < nickm> GeKo: I ask because it seems that warning will occur when
 you have any proxy set alongside ClientTransportPlugin.
 10:11 < nickm> whether the plugins are launched or not
 10:12 < nickm> [in Tor: src/or/config.c, grep for "You have configured
 more than one proxy type"]
 10:13 < GeKo> pointing at 5018 would have been my first guess. I am just
 wondering why that should have broken things...
 10:15 < GeKo> hmm...
 10:15 < nickm> there's no problem in the 5018 code here...
 10:15 < nickm> it just didn't go far enough
 10:15 < nickm> 5018 let you set a bunch of ClientTransportPlugins that you
 did not set before.
 10:16 < nickm> But there was this pre-existing check stopped proxies from
 being set at the same time as clienttransportplugin.
 10:17 < GeKo> I see.
 10:18 < nickm> There's a "make proxies work with client PTs" ticket in
 0.2.6.x, I think
 10:19 < nickm> perhaps as an interim thing you might want to not add all
 those clienttransportplugins when there is a proxy configured.
 10:19 < GeKo> that might be an idea, yes.
 10:19 < nickm> alternatively, you might come up with a fix that extends
 5018 so that non-used clienttransportplugins don't prevent proxies from
 being set.
 10:20 < nickm> The real fix is going to be something like #8402, but I
 make zero promises about merging that code is a remotely good idea at this
 point
 10:20 -zwiebelbot:#tor-dev- [tor#8402: Tor should help its transport proxy
 use a proxy, if needed.]
 10:20 < nickm> s/about/about whether/

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