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 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/blob/HEAD:/proposals/180-pluggable-transport.txt">pluggable
32) transport API</a>, to make it easier to build interoperable programs.
33)     </p>
34) 
35)     <hr>
36) 
37)     <ul>
38)     <li><b>Obfsproxy</b> is a framework for implementing new transport
39)     protocols in C using libevent. See its
40)     <a href="<page projects/obfsproxy>">web page</a>,
41)     <a href="https://gitweb.torproject.org/obfsproxy.git">git repository</a>,
42)     <a href="https://gitweb.torproject.org/obfsproxy.git/blob/HEAD:/doc/obfs2/protocol-spec.txt">obfs2 protocol description</a>,
43)     and
44)     <a href="https://blog.torproject.org/blog/obfsproxy-next-step-censorship-arms-race">blog post</a>.

45)     Maintained by George Kadianakis. <br>
46)     Status: <a href="../projects/obfsproxy.html.en#download">Deployed</a> <a href="https://bridges.torproject.org/?transport=obfs2">(Bridges)</a>

47)     </li>
48) 
49)     <li><b>Flashproxy</b> turns ordinary web browsers into bridges using
50)     websockets, and has a little python stub to hook Tor clients to the
51)     websocket connection. See its
52)     <a href="http://crypto.stanford.edu/flashproxy/">web page</a>,
53)     <a href="https://gitweb.torproject.org/flashproxy.git">git repository</a>,
54)     and
55)     <a href="http://crypto.stanford.edu/flashproxy/flashproxy.pdf">design paper</a>.

56)     Maintained by David Fifield. <br>
57)     Status: <em>Implemented and tested, but there are no bundles yet;
58)     <a href="https://crypto.stanford.edu/flashproxy/#how-to">need
59)     manual setup.</a></em>

60)     </li>
61) 
62)     <li><b>StegoTorus</b> is an Obfsproxy fork that extends it to a)
63)     split Tor streams across multiple connections to avoid packet size
64)     signatures, and b) embed the traffic flows in traces that look like
65)     html, javascript, or pdf. See its
66)     <a href="https://gitweb.torproject.org/stegotorus.git">git repository</a>.

67)     Maintained by Zack Weinberg. <br>
68)     Status: <em>Undeployed</em>

69)     </li>
70) 
71)     <li><b>SkypeMorph</b> transforms Tor traffic flows so they look like
72)     Skype Video. See its
73)     <a href="http://crysp.uwaterloo.ca/software/SkypeMorph-0.5.1.tar.gz">source code</a>
74)     and
75)     <a href="http://cacr.uwaterloo.ca/techreports/2012/cacr2012-08.pdf">design paper</a>.

76)     Maintained by Ian Goldberg. <br>
77)     Status: <em>Undeployed</em>

78)     </li>
79) 
80)     <li><b>Dust</b> aims to provide a packet-based (rather than
81)     connection-based) DPI-resistant protocol. See its
82)     <a href="https://github.com/blanu/Dust">git repository</a>.

83)     Maintained by Brandon Wiley. <br>
84)     Status: <em>Undeployed</em>

85)     </li>
86) 

87)     <li><b>Format-Transforming Encryption</b> transforms Tor traffic
88)     to arbitrary formats using their language descriptions. See
89)     the <a href="http://eprint.iacr.org/2012/494">research

90)     paper</a>. <br>
91)     Status: <em>Undeployed</em>

92)     </li>
93) 

94)     </ul>

95)     <hr>
96) 
97)     <p>
98)     Our goal is to have a wide variety of pluggable transport designs.
99)     Many are at the research phase now, so it's a perfect time to play
100)     with them or suggest new designs. Please let us know if you find or
101)     start other projects that could be useful for making Tor's traffic
102)     flows more DPI-resistant!
103)     </p>