[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #19487 [Core Tor/Tor]: Meek and ReachableAddresses
#19487: Meek and ReachableAddresses
-------------------------------------------------+-------------------------
Reporter: cypherpunks | Owner: dcf
Type: defect | Status: closed
Priority: Medium | Milestone: Tor:
| 0.2.???
Component: Core Tor/Tor | Version: Tor:
| 0.2.8.1-alpha
Severity: Normal | Resolution: fixed
Keywords: ipv6, bridges, pluggable- | Actual Points:
transports, regression, 029-proposed, |
CoreTorTeam201609 |
Parent ID: | Points: 0.2
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):
* keywords: =>
ipv6, bridges, pluggable-transports, regression, 029-proposed,
CoreTorTeam201609
* points: => 0.2
* component: Obfuscation/meek => Core Tor/Tor
* version: => Tor: 0.2.8.1-alpha
* milestone: => Tor: 0.2.???
Comment:
Tor can't know the actual address that a pluggable transport connects to,
unless the pluggable transport tells it. And the pluggable transport
protocol doesn't do that, as far as I know.
So I believe the correct long-term fix here is for Tor to treat all
bridges with transports like SOCKS or HTTP proxies, and warn when their
addresses aren't reachable, but try anyway, rather than failing.
Tor
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19487#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