tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$
3) # Translation-Priority: 3-low
4) 
5) #include "head.wmi" TITLE="Tor Project: Pluggable Transports" CHARSET="UTF-8"
6) <div id="content" class="clearfix">
7)   <div id="breadcrumbs">
8)     <a href="<page index>">Home &raquo; </a>
9)     <a href="<page docs/documentation>">Documentation &raquo; </a>
10)     <a href="<page docs/pluggable-transports>">Pluggable Transports</a>
11)   </div>
12)   <div id="maincol">
13)     <h2>Tor: Pluggable Transports</h2>
14)     <hr>
15) 
16)     <p>
17)     An increasing number of censoring countries are using Deep Packet
18)     Inspection (DPI) to classify Internet traffic flows by protocol.
19)     While Tor uses <a href="<page docs/bridges>">bridge relays</a> to
20)     get around a censor that blocks by IP address, the censor can use
21)     DPI to recognize and filter Tor traffic flows even when they connect
22)     to unexpected IP addresses.
23)     </p>
24) 
25)     <p>

26)     Pluggable Transports (PT) transform the Tor traffic flow between the client

27)     and the bridge. This way, censors who monitor traffic between the
28)     client and the bridge will see innocent-looking transformed traffic
29)     instead of the actual Tor traffic.
30)     External programs can talk to Tor clients and Tor bridges using the <a

31) href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable

32) transport API</a>, to make it easier to build interoperable programs.
33)     </p>
34) 
35)     <hr>
36) 

37)     <h3>Currently deployed PTs</h3>
38)     <p>
39)       These Pluggable Transports are currently deployed in Tor Browser, and you can start using them by <a href="<page download/download-easy>">downloading and using Tor Browser</a>.
40)     </p>
41)     <!-- TODO: make a link to how to config TB to use PTs -->
42) 
43)       <ul>
44) 
45)         <li><a href="https://github.com/Yawning/obfs4/blob/master/doc/obfs4-spec.txt"><b>obfs4</b></a>
46)         is a transport with the same features as <a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a>
47)         but utilizing Dan Bernstein's <a href="http://elligator.cr.yp.to/elligator-20130828.pdf">elligator2</b></a>
48)         technique for public key obfuscation, and the
49)         <a href="https://gitweb.torproject.org/torspec.git/tree/proposals/216-ntor-handshake.txt">ntor protocol</a>
50)         for one-way authentication. This results in a faster protocol. Written in Go.
51)         Maintained by Yawning Angel.
52)         </li>
53)         <!-- TODO: update the link with repo hosted on git.tpo. and make a note that this client supports obfs3 -->
54) 
55)         <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/meek"><b>meek</b></a>
56)         is a transport that uses HTTP for carrying bytes and TLS for
57)         obfuscation. Traffic is relayed through a third-party server
58)         (​Google App Engine). It uses a trick to talk to the third party so
59)         that it looks like it is talking to an unblocked server.
60)         Maintained by David Fifield.
61)         </li>
62)         <!-- TODO: add more info about meek. include amazon and azure and maybe remove google for now -->
63) 
64)         <li><a href="https://fteproxy.org/"><b>Format-Transforming
65)         Encryption</b></a> (FTE) transforms Tor traffic to arbitrary
66)         formats using their language descriptions. See the <a
67)         href="https://kpdyer.com/publications/ccs2013-fte.pdf">research
68)         paper</a>.</li>
69) 
70)         <li><a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a>
71)         is a pluggable transport that protects
72)         against follow-up probing attacks and is also capable of changing
73)         its network fingerprint (packet length distribution,
74)         inter-arrival times, etc.). It's part of the Obfsproxy framework.
75)         Maintained by Philipp Winter.
76)         </li>
77) 
78)         <!-- TODO: it's unclear whether orbot still uses obfsclient or not;
79)                    commenting out untill furthure notice -->
80)         <!-- <li><a href="https://github.com/yawning/obfsclient"><b>obfsclient</b></a>
81)         is a multi-transport pluggable transport proxy (like obfsproxy),
82)         written in C++ that implements the client-side of <em>obfs2</em>,
83)         <em>obfs3</em> and <em>scramblesuit</em>. It's used by
84)         <a href="https://guardianproject.info/apps/orbot/">Orbot</a> on
85)         Android because of the difficulties of using Python applications.
86)         Maintained by Yawning Angel. <br>
87)         </li> -->
88) 
89)       </ul>
90) 
91)       <hr>
92) 
93)       <h3>Deprecated PTs; Removed from Tor Browser</h3>

94)       <br>

95)       <ul>
96)         <!-- TODO: add deprecation note for each PT -->
97)         <li><a href="<page projects/obfsproxy>"><b>Obfsproxy</b></a> is a Python framework for implementing new
98)         pluggable transports. It uses Twisted for its networking needs, and
99)         <a href="https://gitweb.torproject.org/pluggable-transports/pyptlib.git/tree/README.rst">pyptlib</a>
100)         for some pluggable transport-related features. It supports the
101)         <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs2/obfs2-protocol-spec.txt">obfs2</a>
102)         and
103)         <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs3/obfs3-protocol-spec.txt">obfs3</a>
104)         pluggable transports. Maintained by asn.
105)         </li>
106) 
107)         <li><a href="https://crypto.stanford.edu/flashproxy/"><b>Flashproxy</b></a> turns ordinary web browsers into bridges using
108)         websockets, and has a little python stub to hook Tor clients to the
109)         websocket connection. See its
110)         <a href="https://gitweb.torproject.org/flashproxy.git">git repository</a>,
111)         and
112)         <a href="https://crypto.stanford.edu/flashproxy/flashproxy.pdf">design paper</a>.
113)         Maintained by David Fifield.
114)         <!-- # <iframe src="//crypto.stanford.edu/flashproxy/embed.html" width="80" height="15" frameborder="0" scrolling="no"></iframe> -->
115)         </li>
116) 
117)       </ul>
118) 
119)       <hr>
120) 
121)       <h3>Undeployed PTs</h3>

122)       <br>

123)       <!-- TODO: move this section to wiki -->
124)       <!-- TODO: add snowflake -->

125)     <ul>

126) 

127)     <li><b>StegoTorus</b> is an Obfsproxy fork that extends it to a)
128)     split Tor streams across multiple connections to avoid packet size
129)     signatures, and b) embed the traffic flows in traces that look like

130)     HTML, JavasCript, or PDF. See its

131)     <a href="https://gitweb.torproject.org/stegotorus.git">git repository</a>.

132)     Maintained by Zack Weinberg. <br>

133)     </li>
134) 
135)     <li><b>SkypeMorph</b> transforms Tor traffic flows so they look like
136)     Skype Video. See its
137)     <a href="http://crysp.uwaterloo.ca/software/SkypeMorph-0.5.1.tar.gz">source code</a>
138)     and
139)     <a href="http://cacr.uwaterloo.ca/techreports/2012/cacr2012-08.pdf">design paper</a>.

140)     Maintained by Ian Goldberg. <br>

141)     </li>
142) 
143)     <li><b>Dust</b> aims to provide a packet-based (rather than
144)     connection-based) DPI-resistant protocol. See its
145)     <a href="https://github.com/blanu/Dust">git repository</a>.

146)     Maintained by Brandon Wiley. <br>

147)     </li>
148) 
149)     </ul>

150) 
151)     <p> Also see the <emph>unofficial</emph> pluggable transports <a
152)     href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports">wiki
153)     page</a> for more pluggable transport information.</p>
154) 

155)     <hr>
156) 
157)     <p>

158)     Our goal is to have a wide variety of Pluggable Transport designs.

159)     Many are at the research phase now, so it's a perfect time to play
160)     with them or suggest new designs. Please let us know if you find or
161)     start other projects that could be useful for making Tor's traffic
162)     flows more DPI-resistant!
163)     </p>