[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18517 [Tor]: meek is broken in Tor Browser 6.0a3
#18517: meek is broken in Tor Browser 6.0a3
-----------------------------------------------+---------------------------
Reporter: gk | Owner: tbb-team
Type: defect | Status: new
Priority: Very High | Milestone: Tor:
Component: Tor | 0.2.8.x-final
Severity: Normal | Version: Tor:
Keywords: regression must-fix-before-028-rc | 0.2.8.1-alpha
Parent ID: | Resolution:
Reviewer: | Actual Points:
| Points:
| Sponsor: None
-----------------------------------------------+---------------------------
Changes (by teor):
* keywords: regression => regression must-fix-before-028-rc
* version: => Tor: 0.2.8.1-alpha
* component: Tor Browser => Tor
* milestone: => Tor: 0.2.8.x-final
Comment:
Hmm, after thinking about this for a few days, I actually think picking
another dummy IP address and hoping it keeps working in future is a
brittle approach. I'd rather work out why tor is trying to connect to that
address in the first place, when the pluggable transport should be the
thing connecting to it, not tor.
(Am I understanding how pluggable transports work?)
I think what tor should do is:
* if a transport is specified in the Bridge line, and that transport
corresponds to a ClientTransportPlugin line, tor should pass the address
in the bridge line to the pluggable transport, and not try to connect to
that address itself. (The pluggable transport is free to use [obfsproxy]
or ignore [meek] that address.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18517#comment:7>
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