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)     <h1>Tor: Pluggable Transports</h1>

14) 

15)     <hr>

16) 
17)     <h3>Sometimes the Tor network is censored, and you can't connect to
18)     it.</h3>
19) 

20)     <br />

21) 
22)     <p>
23)     An increasing number of censoring countries are using Deep Packet
24)     Inspection (DPI) to classify Internet traffic flows by protocol.
25)     While Tor uses <a href="<page docs/bridges>">bridge relays</a> to
26)     get around a censor that blocks by IP address, the censor can use
27)     DPI to recognize and filter Tor traffic flows even when they connect
28)     to unexpected IP addresses.

29)     </p>
30) 

31)     <h3>Pluggable Transports help you bypass censorship against Tor.</h3>

32) 

33)     <br />

34) 
35)     <p>
36)     Pluggable Transports (PT) transform the Tor traffic flow between the client
37)     and the bridge. This way, censors who monitor traffic between the client
38)     and the bridge will see innocent-looking transformed traffic instead of the
39)     actual Tor traffic.
40)     External programs can talk to Tor clients and Tor bridges using the <a
41)     href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable
42)     transport API</a>, to make it easier to build interoperable programs.

43)     </p>
44) 

45) 

46)     <h3>Learn more:</h3>
47) 

48)     <br />

49) 

50)     <ul>
51)         <li><a href="#user">How to use a Pluggable Transport</a></li>
52)         <li><a href="#operator">How to become a PT bridge operator</a></li>
53)         <li><a href="#developer">How to become a PT developer</a></li>
54)         <li><a href="#list-of-pts">List of PTs organized by their status</a></li>
55)     </ul>
56)     <br /><hr>
57) 
58)     <h2 id="user">How to use PTs to bypass censorship</h2>
59)     <p>If connections to the Tor network are being blocked by your ISP or country, follow these instructions:

60)     </p>

61) 

62)     <a href="$(IMGROOT)/PT/2016-07-how-to-use-PT.png"> <img src="$(IMGROOT)/PT/2016-07-how-to-use-PT.png" width="830" alt="How to use PTs: 1-download tor (send email to gettor@torproject.org); 2 select configure 3; check my isp blocks tor option; 4 select obfs4; 5 press connect" /></a>

63)     <!-- TODO: move alt to instructions in plain text for visually impaird users -->
64) 

65)     <br /><br />
66) 
67)     <hr>
68) 

69)     <h2 id="operator">Become a PT bridge operator:</h2>

70) 

71)     <h3>How to run PTs to help censored users</h3>

72) 
73)     <br />
74) 

75)     <p>
76)     Anyone can set up a PT bridge server and help provide bandwidth to users
77)     who needs it. Once you set up a transport type, your bridge will
78)     automatically advertise support for the transport in its descriptor.
79)     </p>

80) 

81)     <p>
82)     <strong>obfs4</strong> is currently the most effective transport to bypass
83)     censorship. We are asking voluntters to run bridges for it.<br /> To learn
84)     how to run this transport, please visit the <a
85)     href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4proxy">obfs4proxy
86)     wiki page</a>.

87)     </p>
88) 

89)     <p>
90)     <a
91)     href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#BecomeaPTbridgeoperator">Go
92)     to our wiki</a> to learn how to set up other types of PTs.
93)     </p>

94) 
95)     <hr>
96) 
97)     <h2 id="developer">Become a PT developer:</h2>
98) 

99)     <p> The links below are the main documentation for PT developers</p>

100) 
101)     <ul>
102)         <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/GuidelinesForDeployingPTs">Guidelines for deploying Pluggable Transports on Tor Browser</a></li>

103)         <li><a href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">PT technical spec</a></li>

104)         <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/PTEvaluationCriteria">Pluggable Transports Evaluation Criteria</a></li>
105)     </ul>
106) 

107)     <p><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports">Our wiki</a> is also a great source of information, such as how to <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Waystofollowandjointheconversation">get in touch with the community</a>, <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/ideas">ideas for new PTs</a>, how to <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/WorkListForDevsToHelpOutWith">help with PTs already deployed</a> and much more.</p>

108) 

109)     <hr>
110) 

111)     <h2 id="list-of-pts">List of PTs organized by status:</h2>
112) 

113)     <h3>Currently deployed PTs</h3>

114) 
115)     <p>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>.

116)     </p>
117) 
118)       <ul>

119)         <li><a href="https://github.com/Yawning/obfs4/blob/master/doc/obfs4-spec.txt"><b>obfs4</b></a></li>
120)             <ul>
121)             <li><strong>Description:</strong> Is a transport with the same features as <a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a> but utilizing Dan Bernstein's <a href="http://elligator.cr.yp.to/elligator-20130828.pdf">elligator2</b></a> technique for public key obfuscation, and the <a href="https://gitweb.torproject.org/torspec.git/tree/proposals/216-ntor-handshake.txt">ntor protocol</a> for one-way authentication. This results in a faster protocol.</li>
122)             <li><strong>Language:</strong> Go</li>
123)             <li><strong>Maintainer:</strong> Yawning Angel</li>
124)             <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/Obfs4Evaluation">obfs4 Evaluation</a></li>
125)             </ul>

126)         </li>
127)         <!-- TODO: update the link with repo hosted on git.tpo. and make a note that this client supports obfs3 -->
128) 

129)         <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/meek"><b>meek</b></a></li>
130)             <ul>

131)                 <li><strong>Description:</strong> Is a transport that uses HTTP for carrying bytes and TLS for obfuscation. Traffic is relayed through a third-party server (Google App Engine). It uses a trick to talk to the third party so that it looks like it is talking to an unblocked server.</li>

132)                 <li><strong>Language:</strong> Go</li>
133)                 <li><strong>Maintainer:</strong> David Fifield</li>
134)                 <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/MeekEvaluation">meek Evaluation</a></li>
135)             </ul>

136)         </li>
137)         <!-- TODO: add more info about meek. include amazon and azure and maybe remove google for now -->
138) 

139)         <li><a href="https://fteproxy.org/"><b>Format-Transforming Encryption</b></a> (FTE)</li>
140)             <ul>
141)                 <li><strong>Description:</strong> It transforms Tor traffic to arbitrary
142)         formats using their language descriptions. See the <a href="https://kpdyer.com/publications/ccs2013-fte.pdf">research paper</a>.</li>
143)                 <li><strong>Language:</strong> Python/C++</li>
144)                 <li><strong>Maintainger:</strong> Kevin Dyer</li>
145)                 <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/FteEvaluation">FTE Evaluation</a></li>
146)             </ul> 
147)         </li>
148) 
149)         <li><a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a></li>
150)             <ul>
151)                 <li><strong>Description:</strong> Is a pluggable transport that protects against follow-up probing attacks and is also capable of changing its network fingerprint (packet length distribution, inter-arrival times, etc.).</li>
152)                 <li><strong>Language:</strong> Python</li>
153)                 <li><strong>Maintainger:</strong> Philipp Winter</li>
154)                 <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/ScrambleSuitEvaluation"> ScrambleSuit Evaluation</a></li>
155)             </ul>

156)         </li>
157) 
158)         <!-- TODO: it's unclear whether orbot still uses obfsclient or not;
159)                    commenting out untill furthure notice -->
160)         <!-- <li><a href="https://github.com/yawning/obfsclient"><b>obfsclient</b></a>
161)         is a multi-transport pluggable transport proxy (like obfsproxy),
162)         written in C++ that implements the client-side of <em>obfs2</em>,
163)         <em>obfs3</em> and <em>scramblesuit</em>. It's used by
164)         <a href="https://guardianproject.info/apps/orbot/">Orbot</a> on
165)         Android because of the difficulties of using Python applications.
166)         Maintained by Yawning Angel. <br>
167)         </li> -->
168) 
169)       </ul>
170) 

171)     <h3>Undeployed PTs</h3>
172)     <br />

173)       <!-- TODO: move this section to wiki -->
174)       <!-- TODO: add snowflake -->

175)     <ul>

176)     <li><b>StegoTorus</b></li>
177)         <ul>
178)             <li><strong>Description:</strong>is an Obfsproxy fork that extends it to a) split Tor streams across multiple connections to avoid packet size signatures, and b) embed the traffic flows in traces that look like HTML, JavasCript, or PDF. See its <a href="https://gitweb.torproject.org/stegotorus.git">git repository</a>.</li>
179)             <li><strong>Language:</strong> C++</li>
180)             <li><strong>Maintainger:</strong> Zack Weinberg</li>
181)             <li><strong>Evaluation:</strong> none</li>            
182)         </ul> 

183)     </li>
184) 

185)             <li><b>SkypeMorph</b></li>
186)         <ul>
187)             <li><strong>Description:</strong> It transforms Tor traffic flows so they look like Skype Video. See its <a href="http://crysp.uwaterloo.ca/software/SkypeMorph-0.5.1.tar.gz">source code</a> and <a href="http://cacr.uwaterloo.ca/techreports/2012/cacr2012-08.pdf">design paper</a>.</li>
188)             <li><strong>Language:</strong></li>
189)             <li><strong>Maintainger:</strong> Ian Goldberg.</li>
190)             <li><strong>Evaluation:</strong> none</li>            
191)         </ul>

192)     </li>
193) 

194)     <li><b>Dust</b></li>
195)         <ul>
196)             <li><strong>Description:</strong> It aims to provide a packet-based (rather than connection-based) DPI-resistant protocol. See its <a href="https://github.com/blanu/Dust">git repository</a>.</li>
197)             <li><strong>Language:</strong> Python</li>
198)             <li><strong>Maintainger:</strong> Brandon Wiley.</li>
199)             <li><strong>Evaluation:</strong> none</li>            
200)         </ul>

201)     </li>

202) 

203)     </ul>

204) 

205)     <br /><br />

206) 

207)     <p>Our goal is to have a wide variety of Pluggable Transport designs. You can check out a <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/list">full list of Pluggables Transports here</a>.</p>

208) 

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

210)     </p>