...
|
...
|
@@ -44,30 +44,42 @@ transport API</a>, to make it easier to build interoperable programs.
|
44
|
44
|
and
|
45
|
45
|
<a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/HEAD:/doc/obfs3/obfs3-protocol-spec.txt">obfs3</a>
|
46
|
46
|
pluggable transports. Maintained by asn. <br>
|
47
|
|
-
|
48
|
|
- Status: <a href="<page projects/obfsproxy>#download">Deployed</a>
|
|
47
|
+ Status: <a href="#download">Deployed</a>
|
49
|
48
|
</li>
|
50
|
49
|
|
51
|
|
- <li><b>Flashproxy</b> turns ordinary web browsers into bridges using
|
|
50
|
+ <li><a href="https://crypto.stanford.edu/flashproxy/"><b>Flashproxy</b></a> turns ordinary web browsers into bridges using
|
52
|
51
|
websockets, and has a little python stub to hook Tor clients to the
|
53
|
52
|
websocket connection. See its
|
54
|
|
- <a href="https://crypto.stanford.edu/flashproxy/">web page</a>,
|
55
|
53
|
<a href="https://gitweb.torproject.org/flashproxy.git">git repository</a>,
|
56
|
54
|
and
|
57
|
55
|
<a href="https://crypto.stanford.edu/flashproxy/flashproxy.pdf">design paper</a>.
|
58
|
56
|
Maintained by David Fifield.
|
59
|
57
|
# <iframe src="//crypto.stanford.edu/flashproxy/embed.html" width="80" height="15" frameborder="0" scrolling="no"></iframe>
|
60
|
58
|
<br>
|
61
|
|
- Status: <a href="https://crypto.stanford.edu/flashproxy/#how-to">Deployed</a>
|
|
59
|
+ Status: <a href="#download">Deployed</a>
|
62
|
60
|
</li>
|
63
|
61
|
|
64
|
|
- <li><b>ScrambleSuit</b> is a pluggable transport that protects
|
|
62
|
+ <li><a href="https://fteproxy.org/"><b>Format-Transforming
|
|
63
|
+ Encryption</b></a> (FTE) transforms Tor traffic to arbitrary
|
|
64
|
+ formats using their language descriptions. See the <a
|
|
65
|
+ href="https://kpdyer.com/publications/ccs2013-fte.pdf">research
|
|
66
|
+ paper</a>. <br> Status: <a href="#download">Deployed</a> </li>
|
|
67
|
+
|
|
68
|
+ <li><a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a>
|
|
69
|
+ is a pluggable transport that protects
|
65
|
70
|
against follow-up probing attacks and is also capable of changing
|
66
|
71
|
its network fingerprint (packet length distribution,
|
67
|
|
- inter-arrival times, etc.). It's part of the Obfsproxy framework. See its
|
68
|
|
- <a href="http://www.cs.kau.se/philwint/scramblesuit/">official page</a>.
|
|
72
|
+ inter-arrival times, etc.). It's part of the Obfsproxy framework.
|
69
|
73
|
Maintained by Philipp Winter. <br>
|
70
|
|
- Status: <em>In testing</em>
|
|
74
|
+ Status: <em>To be deployed</em>
|
|
75
|
+ </li>
|
|
76
|
+
|
|
77
|
+ <li><b>Meek</b> is a transport that uses HTTP for carrying bytes
|
|
78
|
+ and TLS for obfuscation. Traffic is relayed through a third-party
|
|
79
|
+ server (​Google App Engine). It uses a trick to talk to the third
|
|
80
|
+ party so that it looks like it is talking to an unblocked server.
|
|
81
|
+ Maintained by David Fifield. <br>
|
|
82
|
+ Status: <e>Coming soon</em>
|
71
|
83
|
</li>
|
72
|
84
|
|
73
|
85
|
<li><b>StegoTorus</b> is an Obfsproxy fork that extends it to a)
|
...
|
...
|
@@ -95,13 +107,6 @@ transport API</a>, to make it easier to build interoperable programs.
|
95
|
107
|
Status: <em>Undeployed</em>
|
96
|
108
|
</li>
|
97
|
109
|
|
98
|
|
- <li><b>Format-Transforming Encryption</b> (FTE) transforms Tor traffic
|
99
|
|
- to arbitrary formats using their language descriptions. See
|
100
|
|
- the <a href="https://kpdyer.com/publications/ccs2013-fte.pdf">research
|
101
|
|
- paper</a> and <a href="https://fteproxy.org/">web page</a>. <br>
|
102
|
|
- Status: <em>In testing</em>
|
103
|
|
- </li>
|
104
|
|
-
|
105
|
110
|
</ul>
|
106
|
111
|
|
107
|
112
|
<p> Also see the <emph>unofficial</emph> pluggable transports <a
|