Opened 6 years ago
Last modified 3 years ago
#1170 open enhancement
Implement Pluggable Transport API
| Reported by: | str4d | Owned by: | zzz |
|---|---|---|---|
| Priority: | major | Milestone: | eventually |
| Component: | router/transport | Version: | 0.9.9 |
| Keywords: | anti-censorship | Cc: | |
| Parent Tickets: | Sensitive: | no |
Description
Following discussions at 30C3 and RWC, a new Transport should be implemented that wraps the Pluggable Transport API used by Tor. Any existing PT could then be used with I2P (whether they could be bundled is a separate PT-specific issue).
There is an open ticket with Tor for improving the PT spec to make this easier.
Subtickets
Change History (5)
comment:1 Changed 6 years ago by
comment:2 Changed 5 years ago by
Basic hooks for registering a pluggable transport (from a plugin) in dfff8f25b4b34f60a864c2b81062a3b07a458aaf 0.9.15-3
comment:3 Changed 5 years ago by
| Keywords: | anti-censorship added |
|---|
comment:4 Changed 4 years ago by
| Status: | new → open |
|---|
comment:5 Changed 3 years ago by
| Milestone: | → eventually |
|---|
beginnings of an obfs4 plugin in branch i2p.plugins.obfs4
It is not really a plugin yet and does not use the CSFI hooks added in comment 2 above. This is not a general-purpose plugin that forks an external (go) process and sets up SOCKS server and client ports. But we should probably do that also.
See also https://trac.torproject.org/projects/tor/ticket/10671