Browse code

updated pt page organizing content according to audience

toya authored on15/07/2016 07:17:09
Showing1 changed files
... ...
@@ -10,85 +10,123 @@
10 10
     <a href="<page docs/pluggable-transports>">Pluggable Transports</a>
11 11
   </div>
12 12
   <div id="maincol">
13
-    <h2>Tor: Pluggable Transports</h2>
13
+    <h1>Tor: Pluggable Transports</h1>
14
+    
14 15
     <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.
16
+    
17
+    <h3>Sometimes the Tor network is censored, and you can't connect it.</h3>
18
+    
19
+    <br />
20
+    
21
+    <p>An increasing number of censoring countries are using Deep Packet Inspection (DPI) to classify Internet traffic flows by protocol. While Tor uses <a href="<page docs/bridges>">bridge relays</a> to get around a censor that blocks by IP address, the censor can use DPI to recognize and filter Tor traffic flows even when they connect to unexpected IP addresses.
23 22
     </p>
24 23
 
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.
24
+    <h3>Pluggable Transports help you bypass censorship against Tor.</h3>
25
+    
26
+    <br />
27
+    
28
+    <p>Pluggable Transports (PT) transform the Tor traffic flow between the client and the bridge. This way, censors who monitor traffic between the client and the bridge will see innocent-looking transformed traffic instead of the actual Tor traffic. External programs can talk to Tor clients and Tor bridges using the <a href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable transport API</a>, to make it easier to build interoperable programs.
33 29
     </p>
34 30
 
35
-    <h3>How to use PTs to bypass censorship</h3>
36
-    <p>
37
-      If connections to the Tor network are being blocked by your ISP or
38
-      country, follow these instructions:
31
+
32
+    <h3>Here you will learn:</h3>
33
+    
34
+    <br />
35
+    
36
+    <ul>
37
+        <li><a href="#user">How to use a Pluggable Transport</a></li>
38
+        <li><a href="#operator">How to become a PT bridge operator</a></li>
39
+        <li><a href="#developer">How to become a PT developer</a></li>
40
+        <li><a href="#list-of-pts">List of PTs organized by their status</a></li>
41
+    </ul>
42
+    <br /><hr>
43
+
44
+    <h2 id="user">How to use PTs to bypass censorship</h2>
45
+    <p>If connections to the Tor network are being blocked by your ISP or country, follow these instructions:
39 46
     </p>
40
-    <a href="$(IMGROOT)/PT/2016-07-how-to-use-PT.png">
41
-    <img src="$(IMGROOT)/PT/2016-07-how-to-use-PT.png" width="830"
42
-    alt="How to use PTs: 1-download tor (send email to gettor@torproject.org) 2-select configure 3-check 'my isp blocks tor...'
43
-    4-select obfs4 5-press connect" /></a>
47
+    
48
+    <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>
44 49
     <!-- TODO: move alt to instructions in plain text for visually impaird users -->
45 50
 
51
+    <br /><br />
52
+
53
+    <hr>
54
+
55
+    <h2 id="operator">Become a PT brigde operator:</h2>
56
+
46 57
     <h3>How to run PTs to help censored users</h3>
47
-    <p>
48
-      obfs4 is currently the most effective transport to bypass censorship.
49
-      To learn how to run this transport, please visit the <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4proxy">obfs4proxy wiki page</a>.
58
+
59
+    <br />
60
+
61
+    <p>Anyone can set up a PT bridge server and help provide bandwidth to users who needs it. Once you set up a transport type, your bridge will automatically advertise support for the transport in its descriptor.</p>
62
+
63
+    <p><strong>obfs4</strong> is currently the most effective transport to bypass censorship. We are asking voluntters to run bridges for it.<br />
64
+    To learn how to run this transport, please visit the <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4proxy">obfs4proxy wiki page</a>.
50 65
     </p>
51 66
 
67
+    <p><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#BecomeaPTbridgeoperator">Go to our wiki</a> to learn how to set up other types of PTs.</p>
68
+
69
+    <hr>
70
+
71
+    <h2 id="developer">Become a PT developer:</h2>
72
+
73
+    <p> The links below are the main documentation that will help guide through what you should consider while designing your PT:</p>
74
+
75
+    <ul>
76
+        <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/GuidelinesForDeployingPTs">Guidelines for deploying Pluggable Transports on Tor Browser</a></li>
77
+        <li><a href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">PT technical spec</a>​</li>
78
+        <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/PTEvaluationCriteria">Pluggable Transports Evaluation Criteria</a></li>
79
+    </ul>
80
+
81
+    <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>
82
+
52 83
     <hr>
53 84
 
85
+    <h2 id="list-of-pts">List of PTs organized by status:</h2>
86
+
54 87
     <h3>Currently deployed PTs</h3>
55
-    <p>
56
-      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>.
88
+
89
+    <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>.
57 90
     </p>
58 91
 
59 92
       <ul>
60
-
61
-        <li><a href="https://github.com/Yawning/obfs4/blob/master/doc/obfs4-spec.txt"><b>obfs4</b></a>
62
-        is a transport with the same features as <a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a>
63
-        but utilizing Dan Bernstein's <a href="http://elligator.cr.yp.to/elligator-20130828.pdf">elligator2</b></a>
64
-        technique for public key obfuscation, and the
65
-        <a href="https://gitweb.torproject.org/torspec.git/tree/proposals/216-ntor-handshake.txt">ntor protocol</a>
66
-        for one-way authentication. This results in a faster protocol. Written in Go.
67
-        Maintained by Yawning Angel.
93
+        <li><a href="https://github.com/Yawning/obfs4/blob/master/doc/obfs4-spec.txt"><b>obfs4</b></a></li>
94
+            <ul>
95
+            <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>
96
+            <li><strong>Language:</strong> Go</li>
97
+            <li><strong>Maintainer:</strong> Yawning Angel</li>
98
+            <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/Obfs4Evaluation">obfs4 Evaluation</a></li>
99
+            </ul>
68 100
         </li>
69 101
         <!-- TODO: update the link with repo hosted on git.tpo. and make a note that this client supports obfs3 -->
70 102
 
71
-        <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/meek"><b>meek</b></a>
72
-        is a transport that uses HTTP for carrying bytes and TLS for
73
-        obfuscation. Traffic is relayed through a third-party server
74
-        (​Google App Engine). It uses a trick to talk to the third party so
75
-        that it looks like it is talking to an unblocked server.
76
-        Maintained by David Fifield.
103
+        <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/meek"><b>meek</b></a></li>
104
+            <ul>
105
+                <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>
106
+                <li><strong>Language:</strong> Go</li>
107
+                <li><strong>Maintainer:</strong> David Fifield</li>
108
+                <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/MeekEvaluation">meek Evaluation</a></li>
109
+            </ul>
77 110
         </li>
78 111
         <!-- TODO: add more info about meek. include amazon and azure and maybe remove google for now -->
79 112
 
80
-        <li><a href="https://fteproxy.org/"><b>Format-Transforming
81
-        Encryption</b></a> (FTE) transforms Tor traffic to arbitrary
82
-        formats using their language descriptions. See the <a
83
-        href="https://kpdyer.com/publications/ccs2013-fte.pdf">research
84
-        paper</a>.</li>
85
-
86
-        <li><a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a>
87
-        is a pluggable transport that protects
88
-        against follow-up probing attacks and is also capable of changing
89
-        its network fingerprint (packet length distribution,
90
-        inter-arrival times, etc.). It's part of the Obfsproxy framework.
91
-        Maintained by Philipp Winter.
113
+        <li><a href="https://fteproxy.org/"><b>Format-Transforming Encryption</b></a> (FTE)</li>
114
+            <ul>
115
+                <li><strong>Description:</strong> It transforms Tor traffic to arbitrary
116
+        formats using their language descriptions. See the <a href="https://kpdyer.com/publications/ccs2013-fte.pdf">research paper</a>.</li>
117
+                <li><strong>Language:</strong> Python/C++</li>
118
+                <li><strong>Maintainger:</strong> Kevin Dyer</li>
119
+                <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/FteEvaluation">FTE Evaluation</a></li>
120
+            </ul> 
121
+        </li>
122
+
123
+        <li><a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a></li>
124
+            <ul>
125
+                <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>
126
+                <li><strong>Language:</strong> Python</li>
127
+                <li><strong>Maintainger:</strong> Philipp Winter</li>
128
+                <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/ScrambleSuitEvaluation"> ScrambleSuit Evaluation</a></li>
129
+            </ul>
92 130
         </li>
93 131
 
94 132
         <!-- TODO: it's unclear whether orbot still uses obfsclient or not;
... ...
@@ -104,78 +142,49 @@ transport API</a>, to make it easier to build interoperable programs.
104 142
 
105 143
       </ul>
106 144
 
107
-      <hr>
108
-
109
-      <h3>Deprecated PTs; Removed from Tor Browser</h3>
110
-      <br>
111
-      <ul>
112
-        <!-- TODO: add deprecation note for each PT -->
113
-        <li><b>Obfsproxy</b> is a Python framework for implementing new
114
-        pluggable transports. It uses Twisted for its networking needs, and
115
-        <a href="https://gitweb.torproject.org/pluggable-transports/pyptlib.git/tree/README.rst">pyptlib</a>
116
-        for some pluggable transport-related features. It supports the
117
-        <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs2/obfs2-protocol-spec.txt">obfs2</a>
118
-        and
119
-        <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs3/obfs3-protocol-spec.txt">obfs3</a>
120
-        pluggable transports. Maintained by asn.
121
-        </li>
122
-
123
-        <li><a href="https://crypto.stanford.edu/flashproxy/"><b>Flashproxy</b></a> turns ordinary web browsers into bridges using
124
-        websockets, and has a little python stub to hook Tor clients to the
125
-        websocket connection. See its
126
-        <a href="https://gitweb.torproject.org/flashproxy.git">git repository</a>,
127
-        and
128
-        <a href="https://crypto.stanford.edu/flashproxy/flashproxy.pdf">design paper</a>.
129
-        Maintained by David Fifield.
130
-        <!-- # <iframe src="//crypto.stanford.edu/flashproxy/embed.html" width="80" height="15" frameborder="0" scrolling="no"></iframe> -->
131
-        </li>
132
-
133
-      </ul>
134
-
135
-      <hr>
136
-
137
-      <h3>Undeployed PTs</h3>
138
-      <br>
145
+    <h3>Undeployed PTs</h3>
146
+    <br />
139 147
       <!-- TODO: move this section to wiki -->
140 148
       <!-- TODO: add snowflake -->
141 149
     <ul>
142
-
143
-    <li><b>StegoTorus</b> is an Obfsproxy fork that extends it to a)
144
-    split Tor streams across multiple connections to avoid packet size
145
-    signatures, and b) embed the traffic flows in traces that look like
146
-    HTML, JavasCript, or PDF. See its
147
-    <a href="https://gitweb.torproject.org/stegotorus.git">git repository</a>.
148
-    Maintained by Zack Weinberg. <br>
150
+    <li><b>StegoTorus</b></li>
151
+        <ul>
152
+            <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>
153
+            <li><strong>Language:</strong> C++</li>
154
+            <li><strong>Maintainger:</strong> Zack Weinberg</li>
155
+            <li><strong>Evaluation:</strong> none</li>            
156
+        </ul> 
149 157
     </li>
150 158
 
151
-    <li><b>SkypeMorph</b> transforms Tor traffic flows so they look like
152
-    Skype Video. See its
153
-    <a href="http://crysp.uwaterloo.ca/software/SkypeMorph-0.5.1.tar.gz">source code</a>
154
-    and
155
-    <a href="http://cacr.uwaterloo.ca/techreports/2012/cacr2012-08.pdf">design paper</a>.
156
-    Maintained by Ian Goldberg. <br>
159
+            <li><b>SkypeMorph</b></li>
160
+        <ul>
161
+            <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>
162
+            <li><strong>Language:</strong></li>
163
+            <li><strong>Maintainger:</strong> Ian Goldberg.</li>
164
+            <li><strong>Evaluation:</strong> none</li>            
165
+        </ul>
157 166
     </li>
158 167
 
159
-    <li><b>Dust</b> aims to provide a packet-based (rather than
160
-    connection-based) DPI-resistant protocol. See its
161
-    <a href="https://github.com/blanu/Dust">git repository</a>.
162
-    Maintained by Brandon Wiley. <br>
168
+    <li><b>Dust</b></li>
169
+        <ul>
170
+            <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>
171
+            <li><strong>Language:</strong> Python</li>
172
+            <li><strong>Maintainger:</strong> Brandon Wiley.</li>
173
+            <li><strong>Evaluation:</strong> none</li>            
174
+        </ul>
163 175
     </li>
164
-
176
+    
165 177
     </ul>
178
+    
179
+    <br /><br />
166 180
 
167 181
     <p> Also see the <emph>unofficial</emph> pluggable transports <a
168 182
     href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports">wiki
169 183
     page</a> for more pluggable transport information.</p>
170 184
 
171
-    <hr>
185
+    <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>
172 186
 
173
-    <p>
174
-    Our goal is to have a wide variety of Pluggable Transport designs.
175
-    Many are at the research phase now, so it's a perfect time to play
176
-    with them or suggest new designs. Please let us know if you find or
177
-    start other projects that could be useful for making Tor's traffic
178
-    flows more DPI-resistant!
187
+    <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!
179 188
     </p>
180 189
 
181 190
   </div>