[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30477 [Core Tor/Tor]: Tor should self-test reachability of TCP listeners exposed by PT's
#30477: Tor should self-test reachability of TCP listeners exposed by PT's
-------------------------------------------------+-------------------------
Reporter: ahf | Owner: (none)
Type: task | Status: new
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version: Tor:
| unspecified
Severity: Normal | Resolution:
Keywords: tor-pt, network-team-roadmap- | Actual Points:
november |
Parent ID: #30471 | Points:
Reviewer: | Sponsor:
| Sponsor30-must
-------------------------------------------------+-------------------------
Comment (by phw):
Replying to [comment:7 teor]:
> It wouldn't be that hard to teach Tor bridges to self-test their PT
addresses via an Exit, like we already do with DirPorts. As a bonus step,
we might even want to test that the port speaks the PT protocol.
[[br]]
This sounds great because it's consistent with how a bridge's vanilla port
is tested and the sooner we can tell an operator that something's wrong,
the better. The bonus step is helpful in some edge cases: we recently had
a bridge with an open obfs4 port but obfs4 connections failed. It turned
out that obfs4proxy was unable to talk to tor because a local security
policy prevented obfs4proxy from connecting to the ExtORPort.
The only downside I see is that it won't work for a UDP-based transport –
if we ever end up deploying one.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30477#comment:8>
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