[tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Jun 13 17:48:29 UTC 2019
#29285: Improve the PT spec and how PTs interface with Tor
-------------------------------------------------+-------------------------
Reporter: cohosh | Owner: phw
Type: project | Status:
| assigned
Priority: High | Milestone:
Component: Circumvention/Pluggable transport | Version:
Severity: Normal | Resolution:
Keywords: network-team-roadmap-2019-Q1Q2, | Actual Points:
anti-censorship-roadmap |
Parent ID: | Points: 15
Reviewer: | Sponsor:
| Sponsor28-must
-------------------------------------------------+-------------------------
Changes (by mcs):
* cc: brade, mcs (added)
Comment:
Replying to [comment:7 dcf]:
> Replying to [comment:5 phw]:
> > And here's an incomplete list of existing library implementations:
>
> Really there are two types of PT implementations, or three if you count
PT 2.0 additions. There aren't really standard names for these.
> 1. IPC manager/dispatcher. As far as I know, tor and
[https://github.com/twisteroidambassador/ptadapter] are the only two
implementations of this. This is the thing that sets e.g.
`TOR_PT_MANAGED_TRANSPORT_VER` and manages subprocesses of type (2).
The module within Tor Launcher that implements Moat (interactive bridge
retrieval) is another example of the above. We did that so we could reuse
your Meek PT implementation. See https://gitweb.torproject.org/tor-
launcher.git/tree/src/modules/tl-bridgedb.jsm?h=maint-0.2.18#n188
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29285#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list