Browse code

Update bridge docu to not recommend port 443 anymore

This aids scanning resistance as per ticket #13996

Sebastian Hahn authored on24/04/2015 10:27:13
Showing1 changed files
... ...
@@ -281,7 +281,7 @@
281 281
     the bridges.  Almost instantly, you'll receive a reply that includes:
282 282
     </p>
283 283
     <pre>
284
-    Here are your bridge:
284
+    Here are your bridges:
285 285
 
286 286
      60.16.182.53:9001
287 287
      87.237.118.139:444
... ...
@@ -323,19 +323,13 @@
323 323
     your torrc file</a> to be just these four lines:<br>
324 324
     <pre><code>
325 325
     SocksPort 0
326
-    ORPort 443
326
+    ORPort auto
327 327
     BridgeRelay 1
328 328
     Exitpolicy reject *:*
329 329
     </code></pre></li>
330 330
     </ul>
331 331
     </p>
332 332
 
333
-    <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
334
-    on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
335
-    href="<page docs/faq>#HowcanImakemyrelayaccessibletopeoplestuckbehindrestrictivefirewalls">some
336
-    complex port forwarding</a>.
337
-    </p>
338
-
339 333
     <p>
340 334
     When configured as a bridge, your server will <b>not</b> appear in the public
341 335
     Tor network.
Browse code

Remove vidalia-related docs and downloads

The downloads are horribly outdated, the docs are confusing and long.
Without a proper Vidalia maintainer and someone making packages, this
has no future.

Sebastian Hahn authored on08/02/2015 17:55:35
Showing1 changed files
... ...
@@ -327,9 +327,6 @@
327 327
     BridgeRelay 1
328 328
     Exitpolicy reject *:*
329 329
     </code></pre></li>
330
-    <li><a href="<page docs/tor-doc-relay>">or using Vidalia</a>:<br>
331
-    <img src="$(IMGROOT)/vidalia-bridges-setup.png" alt="Vidalia's Sharing
332
-    settings page"></li>
333 330
     </ul>
334 331
     </p>
335 332
 
... ...
@@ -346,10 +343,8 @@
346 343
 
347 344
     <p>
348 345
     Your bridge relay will automatically publish its address to the bridge
349
-    authority, which will give it out via https or email as above. You can
350
-    also tell a user about your bridge directly: if you're using Vidalia,
351
-    you can copy-and-paste the bridge address from the Settings window. If
352
-    you're on Linux or BSD, you can construct the bridge address manually
346
+    authority, which will give it out via https or email as above.
347
+    You can construct the bridge address
353 348
     using the <a href="#Understanding">format above</a> (you can find the
354 349
     fingerprint in your Tor log files or in <tt>/var/lib/tor/fingerprint</tt>
355 350
     depending on your platform).
Browse code

Make the bridge user documentation usable again

Matthew Finkel authored on14/01/2015 18:23:49
Showing1 changed files
... ...
@@ -14,7 +14,7 @@
14 14
     <a href="<page docs/documentation>">Documentation &raquo; </a>
15 15
     <a href="<page docs/bridges>">Bridges</a>
16 16
   </div>
17
-  <div id="maincol"> 
17
+  <div id="maincol">
18 18
     <a id="BridgeIntroduction"></a>
19 19
     <h2><a class="anchor" href="#BridgeIntroduction">Tor: Bridges</a></h2>
20 20
     <hr>
... ...
@@ -22,106 +22,106 @@
22 22
     <p>
23 23
     <img width="7%" height="7%" style="float: left;" src="$(IMGROOT)/icon-Obfsproxy.jpg">
24 24
     <b>Tip:</b>
25
-    Having trouble connecting to Tor even when using bridges? You will
26
-    need to use <b>pluggable transports</b> and <b>obfuscated
27
-    bridges</b>. <a class="anchor" href="#PluggableTransports">Click
28
-    here for more information</a>.
25
+    Having trouble connecting to Tor? You may need to use a different <b>pluggable
26
+    transport</b>. <a class="anchor" href="#PluggableTransports">Click here for
27
+    more information</a>.
29 28
     </p>
30
-    
29
+
31 30
     <p>
32 31
     Bridge relays (or "bridges" for short) are Tor relays that aren't listed in
33 32
     the main Tor directory. Since there is no complete public list of them, even if
34 33
     your ISP is filtering connections to all the known Tor relays, they probably
35 34
     won't be able to block all the bridges. If you suspect your access to the
36
-    Tor network is being blocked, you may want to use the bridge feature of Tor.
35
+    Tor network is being blocked, you may want to use bridges.
37 36
     </p>
38
-    
37
+
39 38
     <p>
40 39
     The addition of bridges to Tor is a step forward in the blocking
41 40
     resistance race. It is perfectly possible that even if your ISP filters
42 41
     the Internet, you do not require a bridge to use Tor. So you should try
43 42
     to use Tor without bridges first, since it might work.
44 43
     </p>
45
-    
44
+
46 45
     <p>
47 46
     Note that it's also possible that Tor is non-functional for other
48
-    reasons. The latest version of <a href="<page projects/torbrowser>">The
49
-    Tor Browser Bundle</a> on Windows tries to give you better hints about
50
-    why Tor is having problems connecting. You should also read <a
51
-    href="<wikifaq>#IinstalledTorandPolipobutitsnotworking.">the
47
+    reasons. The latest version of <a href="<page projects/torbrowser>">
48
+    Tor Browser</a> tries to give you better hints about why Tor is having
49
+    problems connecting. You should also read <a href="<page docs/faq>#DoesntWork">the
52 50
     FAQ about problems with running Tor properly</a> when you have issues.
53
-    If you feel that the issue is clearly blocking, or you'd simply like to try
54
-    because you're unsure or feeling adventurous, please read on. Ensure
55
-    that you're using the <a href="<page download/download>#Dev">latest 0.2.3.x or
56
-    0.2.4.x bundle for your platform</a>.
51
+    If you feel that the issue is clearly related to Tor being blocked, or
52
+    you'd simply like to try because you're unsure or feeling adventurous,
53
+    please read on. Ensure that you're using the <a href="<page download/download>#Dev">latest
54
+    Tor Browser for your platform</a>.
57 55
     </p>
58
-    
56
+
59 57
     <p>
60
-    To use a bridge, you'll need to locate one. Furthermore, you'll need to
61
-    configure Tor with whatever bridge address you intend to use. You'll do this
62
-    with Vidalia, the Tor controller.
63
-    If your Internet connection requires the use of a proxy, you'll probably
64
-    need to configure Vidalia to do so first. If you don't think you need
65
-    to configure a proxy for your Internet connection, you probably don't.
66
-    Give it a try and if you have issues, ask us for help.
58
+    To use a bridge, you have two options. Tor Browser now provides some
59
+    bridges by default. You can enable these easily. Unfortunately, because
60
+    these bridges are publically distributed, it is easy for censors to block
61
+    some of them, so some of them may not work. In this case, you'll need to
62
+    locate different bridges. Furthermore, you'll need to configure Tor Browser
63
+    with whichever bridge address you intend to use. If your Internet connection
64
+    requires the use of a proxy, you'll probably need to configure Tor Browser
65
+    to use it first. If you don't think you need to configure a proxy for your
66
+    Internet connection, you probably don't. Give it a try and if you have
67
+    issues, <a href="<page about/contact>#support">ask us for help</a>.
67 68
     </p>
68
-    
69
-    <p>Freedom House has produced a video on how to get and use Tor bridges.
70
-    If you don't see a video below, view it at <a
71
-    href="http://www.youtube.com/thetorproject">Youtube:
72
-    Freedom4Internet</a> Know of a better video, or one translated into
73
-    your language?  Let us know!</p>
74
-    
75
-    <div class="center">
76
-    <p><video id="v1" src="https://media.torproject.org/video/2009-using-a-bridge-relay-to-access-tor.ogv" autobuffer="true" controls="controls"></video></p>
77
-    </div>
78
-    
69
+
79 70
     <p>
80
-    At the moment, you can get a bridge by visiting
81
-    <a href="https://bridges.torproject.org/">https://bridges.torproject.org/</a>
82
-    with your web browser. If this page is filtered for you, and you
83
-    don't have any other proxies or ways to reach it, there are <a
84
-    href="#FindingMore">other ways to find bridges</a> too.
71
+    <ul>
72
+    <li><a href="#PluggableTransports">Obfuscated Bridges and Pluggable Transports</a></li>
73
+    <li><a href="#Understanding">Understanding Bridge Configuration Lines</a></li>
74
+    <li><a href="#AddTorNotWorks">Adding bridges in Tor Browser when Tor doesn't work</a></li>
75
+    <li><a href="#AddTorWorks">Adding bridges in Tor Browser when Tor does work</a></li>
76
+    <li><a href="#FindingMore">Finding more bridges for Tor</a></li>
77
+    </ul>
85 78
     </p>
86
-    
79
+
87 80
     <a id="PluggableTransports"></a>
88
-    <h2><a class="anchor" href="#PluggableTransports">Obfuscated Bridges and Pluggable Transports</a></h2>
81
+    <h2><a class="anchor" href="#PluggableTransports">Pluggable Transports</a></h2>
89 82
     <hr>
90
-    
91
-    <p> Lately, censors have found ways to block Tor even when clients
92
-    are using bridges. They usually do this by installing boxes in
93
-    ISPs that peek at network traffic and detect Tor; when Tor is
94
-    detected they block the traffic flow.
83
+
84
+    <p>Over the last few years, censors have found ways to block Tor even when
85
+    clients are using bridges. They usually do this by installing special
86
+    boxes at ISPs that peek into network traffic and detect Tor; when Tor
87
+    is detected they block the traffic flow.
95 88
     </p>
96 89
 
97 90
     <p>To circumvent such sophisticated censorship Tor introduced
98
-    <i>obfuscated bridges</i>. These bridges use special plugins
99
-    called <i>pluggable transports</i> which obfuscate the traffic
100
-    flow of Tor, making its detection harder.
91
+    <a href="<page docs/pluggable-transports>"><i>pluggable transports</i></a>.
92
+    These transports manipulate all Tor traffic between the client and its
93
+    first hop such that it is not identifiable as a Tor connection. If the
94
+    censor can't decide if the connection is a Tor connection, then they are
95
+    less likely to block it.</p>
101 96
 
102
-    To connect to obfuscated bridges you need to use the <a
103
-    href="<page projects/obfsproxy>#download">Obfsproxy
104
-    Tor Browser Bundle</a>. The bundle includes some pre-configured
105
-    obfsproxy bridges and you can get more from <a
106
-    href=https://bridges.torproject.org/?transport=obfs2>BridgeDB</a>
97
+    <p>Sadly, pluggable transports are not immune to detection, if a censor
98
+    is given enough time. In the past, we promoted obfs and obfs2 as safe
99
+    transports. These are now deprecated and were replaced by obfs3,
100
+    scramblesuit, fte, and obfs4.</p>
101
+
102
+    <p>Bridges which support pluggable transports can be used with Tor Browser
103
+    easily. Tor Browser includes some pre-configured bridges and you can get
104
+    more from <a href="#FindingMore">BridgeDB</a>, if those don't work.</p>
107 105
 
108 106
     <a id="Understanding"></a>
109
-    <h2><a class="anchor" href="#Understanding">Understanding bridges</a></h2><hr>
107
+    <h2><a class="anchor" href="#Understanding">Understanding A Bridge Configuration Line</a></h2>
108
+    <hr>
110 109
     <p>
111
-    As an example, you'll get a bridge entry that looks like the
112
-    following:
110
+    As an example, when you obtain a bridge from https://bridges.torproject.org,
111
+    you'll get a bridge entry that looks like the following:
113 112
     </p>
114 113
     <pre><samp>
115
-    bridge 141.201.27.48:443 4352e58420e68f5e40bf7c74faddccd9d1349413
114
+    141.201.27.48:443 4352e58420e68f5e40bf7c74faddccd9d1349413
116 115
     </samp>
117 116
     </pre>
118
-    
117
+
119 118
     <p>
120 119
     Understanding the components of a bridge line isn't strictly required
121 120
     but may prove useful. You can skip this section if you'd like.<br>
122
-    The first element is the IP address: <tt>'141.201.27.48'</tt><br>
123
-    The second element is the port: <tt>'443'</tt><br>
124
-    The third element, the fingerprint, is optional:
121
+    The first element is the IP address of the bridge: <tt>'141.201.27.48'</tt><br>
122
+    The second element is the port number: <tt>'443'</tt><br>
123
+    The third element, the fingerprint (unique identifier of the
124
+    bridge), is optional:
125 125
     <tt>'4352e58420e68f5e40bf7c74faddccd9d1349413'</tt><br>
126 126
 
127 127
     <p>
... ...
@@ -131,82 +131,188 @@
131 131
     <p>
132 132
     If your bridge line looks like this:
133 133
     <pre><samp>
134
-    bridge obfs2 141.201.27.48:420 4352e58420e68f5e40bf7c74faddccd9d1349413
134
+    obfs3 141.201.27.48:420 4352e58420e68f5e40bf7c74faddccd9d1349413
135 135
     </samp>
136 136
     </pre>
137 137
 
138
-    The second element is the name of the pluggable transport
138
+    The first element is the name of the pluggable transport
139 139
     technology used by the bridge. For example, in the case above, the
140
-    bridge is using the <i>obfs2</i> pluggable transport.
140
+    bridge is using the <i>obfs3</i> pluggable transport.
141 141
     </p>
142 142
 
143 143
     <a id="UsingBridges"></a>
144
-    <h2><a class="anchor" href="#UsingBridges">Using bridges with Tor and
145
-    Vidalia</a></h2>
144
+    <h2><a class="anchor" href="#UsingBridges">Using bridges with Tor
145
+    Browser</a></h2>
146 146
     <hr>
147
-    
148
-    <p>
149
-    To use the example bridge address above, go to Vidalia's Network settings
150
-    page, and click "My ISP blocks connections to the Tor network".  Add each
151
-    bridge address one at a time in the Vidalia Network settings page,
152
-    by pasting it into the "Add a Bridge" window and then clicking the "+"
153
-    sign. Adding a bridge is pictured below:
154
-    </p>
155
-    
147
+
148
+    <ul>
149
+    <li><a href="#AddTorNotWorks">Adding bridges in Tor Browser when Tor doesn't work</a></li>
150
+    <li><a href="#AddTorWorks">Adding bridges in Tor Browser when Tor does work</a></li>
151
+    </ul>
152
+
153
+    <a id="AddTorNotWorks"></a>
154
+    <h3><a href="#AddTorNotWorks">Adding bridges in Tor Browser when Tor <em>does not</em> work:</a></h3>
155
+    <hr>
156
+
157
+    <p>First, you should read <a href="<page docs/faq>#DoesntWork">the
158
+    FAQ about problems with running Tor properly</a> when you have issues.
159
+    Sometimes Tor does not work due to a silly mistake rather than your
160
+    ISP interfering with your Internet connection.</p>
161
+
156 162
     <br><br>
157
-    <img src="$(IMGROOT)/vidalia-bridges.png" alt="Vidalia's Network settings page">
163
+    <h3>1) To add a bridge, follow the instructions on screen. Click the
164
+        "Configure" button.
165
+    </h3>
166
+    <br/>
167
+    <img src="$(IMGROOT)/tb-tor-launcher-startup.png" alt="Tor Browser's Initial Configuration page">
168
+    <br><br><br>
169
+    <h3>2) If you must configure a proxy then select "Yes" and enter the
170
+        details on the following page.
171
+        <br/>If you do not use a proxy then select "No" and click "Next".
172
+        <br/>If you do not know if you must configure a proxy then you likely
173
+        do not need to do it.
174
+    </h3>
175
+    <br/>
176
+    <img src="$(IMGROOT)/tb-tor-launcher-no-proxy.png" alt="Tor Browser's Proxy page">
177
+    <br><br><br>
178
+    <h3>3) After you configure a proxy or skip over that configuration page,
179
+        the following page asks "Does your Internet Service Provider (ISP)
180
+        block or otherwise censor connections to the Tor Network?". Select
181
+        "Yes" and then click "Next".</h3>
182
+    <br/>
183
+    <img src="$(IMGROOT)/tb-tor-launcher-isp-interference.png" alt="Tor Browser's Bridge page">
184
+    <br><br><br>
185
+    <h3>4) Now you have two configuration options. You can use bridges which are
186
+        preconfigured and provided with Tor Browser, or you can specify your
187
+        own bridge(s).</h3>
188
+    <br/>
189
+    <img src="$(IMGROOT)/tb-tor-launcher-bridges-options.png" alt="Tor Browser's Bridge Configuration page">
190
+    <br><br><br>
191
+    <h3>5a) If you want to use one of the provided bridges, then choose the
192
+    transport type you want to use. obfs3 is currently the recommend
193
+    type, but depending on where you are located another type may work better
194
+    for you. If you have any questions, please <a href="<page about/contact>#support">contact
195
+    us.</a></h3>
196
+    <br/>
197
+    <img src="$(IMGROOT)/tb-tor-launcher-bridges-provided.png" alt="Tor Browser's Bridge Configuration page - provided bridges">
198
+    <br><br><br>
199
+    <h3>5b) Alternatively, if you want to use a <a href="#FindingMore">custom
200
+    bridge</a>, then select "Enter custom bridges" and copy-and-paste the
201
+    bridge information into the textbox.
202
+    </h3>
203
+    <br/>
204
+    <img src="$(IMGROOT)/tb-tor-launcher-bridges-custom.png" alt="Tor Browser's Bridge Configuration page - provided bridges">
205
+    <br><br><br>
206
+    <h3>6) After you decide which bridges you want to use, click "Connect".
207
+    Tor should now be able to load successfully and the browser window
208
+    should appear.</h3>
209
+    <br/>
210
+    <img src="$(IMGROOT)/tb-frontpage.png" alt="Tor Browser's Front Page">
211
+    <br><br><br><br>
212
+
213
+    <a id="AddTorWorks"></a>
214
+    <h3><a href="#AddTorWorks">Adding bridges in Tor Browser when Tor <em>does</em> work:</a></h3>
215
+    <hr>
216
+
217
+    <p>The following instructions assume Tor Browser successfully loads and
218
+    you are able to surf the web. If you do not see the web browser when you
219
+    run Tor Browser (like in step (1) below), you may need to follow the
220
+    <a href="#AddTorNotWorks">instructions above</a>.
221
+
158 222
     <br><br>
159
-    
160
-    <p>
161
-    You'll want to add as many bridge addresses as you know about, since
162
-    additional bridges will increase reliability. One bridge should be enough
163
-    to reach the Tor network, but if you only have one bridge and it goes
164
-    down, you will be cut off from the Tor network.
165
-    </p>
223
+    <h3>1) Start Tor Browser:</h3>
224
+    <br>
225
+    <img src="$(IMGROOT)/tb-frontpage.png" alt="Tor Browser's Front Page">
226
+    <br><br><br>
227
+    <h3>2) To begin using bridges, open Tor Browser's Network Settings:</h3>
228
+    <br>
229
+    <img src="$(IMGROOT)/tb-tor-button-menu.png" alt="Tor Browser's TorButton Menu">
230
+    <br><br><br>
231
+    <h3>3) Select "My Internet Service Provider (ISP) blocks connections to the Tor network":</h3>
232
+    <br>
233
+    <img src="$(IMGROOT)/tb-bridge-networksettings.png" alt="Tor Browser's Network Settings page">
234
+    <br><br><br>
235
+    <h3>4) Now you have two configuration options. You can use bridges which are
236
+        preconfigured and provided with Tor Browser, or you can specify your
237
+        own bridge(s).</h3>
238
+    <br>
239
+    <img src="$(IMGROOT)/tb-bridges-options-from-browser.png" alt="Tor Browser's TorButton Menu">
240
+    <br><br><br>
241
+    <h3>5a) If you want to use one of the provided bridges, then choose the
242
+    transport type you want to use. obfs3 is currently the recommend
243
+    type, but depending on where you are located another type may work better
244
+    for you. If you have any questions, please <a href="<page about/contact>#support">contact
245
+    us.</a></h3>
246
+    <br>
247
+    <img src="$(IMGROOT)/tb-bridges-provided-from-browser.png" alt="My Internet Service Provider (ISP) blocks connections to the Tor network">
248
+    <br><br><br>
249
+    <h3>5b) Alternatively, if you want to use a <a href="#FindingMore">custom
250
+    bridge</a>, then select "Enter custom bridges" and copy-and-paste the
251
+    bridge information into the textbox.
252
+    </h3>
253
+    <br>
254
+    <img src="$(IMGROOT)/tb-bridges-custom-from-browser.png" alt="Add bridges in the custom bridges textbox">
255
+    <br><br><br>
166 256
 
167 257
     <p>
168
-    <img width="7%" height="7%" style="vertical-align:middle" src="$(IMGROOT)/icon-Obfsproxy.jpg">
169
-         <span><b>Pluggable transports tip:</b></span>
258
+    Tor will only use one bridge at a time, but it is good to add more than one
259
+    bridge so you can continue using Tor even if your first bridge becomes
260
+    unavailable.
170 261
     </p>
171
-    <p>
262
+    <br><br>
172 263
 
173
-    If you have managed to get hold of some obfuscated bridge
174
-    addresses, you should add them in Vidalia in the same fashion that
175
-    you add normal bridges. Just paste the bridge line into the "Add a
176
-    bridge" window:
177 264
 
178
-    <br><br>
179
-    <img src="$(IMGROOT)/vidalia_add_obfsbridge.png" alt="Add obfuscated bridge in Vidalia">
180
-    <br><br>
181
-    
182 265
     <a id="FindingMore"></a>
183 266
     <h2><a class="anchor" href="#FindingMore">Finding more bridges for Tor</a></h2>
184 267
     <hr>
185
-    
268
+
186 269
     <p>
187
-    Another way to find public bridge addresses is to send mail to
188
-    bridges@bridges.torproject.org with the line "get bridges" by itself in the
189
-    body of the mail. You'll need to send this request from a gmail
190
-    account, though &mdash; otherwise we make it too easy for an attacker
191
-    to make a lot of email addresses and learn about all the bridges.
192
-    Almost instantly, you'll receive a reply that includes:
270
+    If you need to get bridges, you can get a bridge by visiting
271
+    <a href="https://bridges.torproject.org/">https://bridges.torproject.org/</a>
272
+    with your web browser.
273
+    </p>
274
+
275
+    <p>
276
+    You can also get bridges by sending mail to bridges@bridges.torproject.org
277
+    with the line "get bridges" by itself in the body of the mail. You'll need
278
+    to send this request from a Gmail, Riseup!, or Yahoo! account, though
279
+    &mdash; we only accept these providers because otherwise we make it too
280
+    easy for an attacker to make a lot of email addresses and learn about all
281
+    the bridges.  Almost instantly, you'll receive a reply that includes:
193 282
     </p>
194 283
     <pre>
195
-    Here are your bridge relays:
284
+    Here are your bridge:
285
+
286
+     60.16.182.53:9001
287
+     87.237.118.139:444
288
+     60.63.97.221:443
196 289
 
197
-     bridge 60.16.182.53:9001
198
-     bridge 87.237.118.139:444
199
-     bridge 60.63.97.221:443
290
+    </pre>
291
+    <p>
292
+    Similarly, if you need bridges with a specific pluggable transport, the
293
+    process is just as easy. First, decide which type you want. Currently we
294
+    provide obfs2, obfs3, scramblesuit, and fte. If you don't know which one
295
+    you should choose, then obfs3 is usually a good choice. Send an email to
296
+    bridges@bridges.torproject.org with "get transport obfs3" by itself in
297
+    the body of the email (replace "obfs3" with whichever pluggable transport
298
+    you want to use). You should receive an email like this:
299
+    </p>
300
+    <pre>
301
+    Here are your bridges:
200 302
 
303
+      obfs3 60.16.182.53:9001 cc8ca10a63aae8176a52ca5129ce816d011523f5
304
+      obfs3 87.237.118.139:444 0ed110497858f784dfd32d448dc8c0b93fee20ca
305
+      obfs3 60.63.97.221:443 daa5e435819275f88d695cb7fce73ed986878cf3
201 306
     </pre>
202 307
     <p>
203
-    Once you've received the email with bridge information, you can continue the Vidalia configuration steps outlined <a href="#UsingBridges">above</a>.
308
+    Once you've received the email with bridge information, you can
309
+    continue the configuration steps outlined <a href="#UsingBridges">above</a>.
204 310
     </p>
205
-    
311
+
206 312
     <a id="RunningABridge"></a>
207 313
     <h2><a class="anchor" href="#RunningABridge">Running a Tor Bridge</a></h2>
208 314
     <hr>
209
-    
315
+
210 316
     <p>
211 317
     If you want to help out, you should <a href="<page
212 318
     docs/faq>#RelayOrBridge">decide whether you want to run a normal Tor
... ...
@@ -226,18 +332,18 @@
226 332
     settings page"></li>
227 333
     </ul>
228 334
     </p>
229
-    
335
+
230 336
     <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
231 337
     on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
232 338
     href="<page docs/faq>#HowcanImakemyrelayaccessibletopeoplestuckbehindrestrictivefirewalls">some
233 339
     complex port forwarding</a>.
234 340
     </p>
235
-    
341
+
236 342
     <p>
237 343
     When configured as a bridge, your server will <b>not</b> appear in the public
238 344
     Tor network.
239 345
     </p>
240
-    
346
+
241 347
     <p>
242 348
     Your bridge relay will automatically publish its address to the bridge
243 349
     authority, which will give it out via https or email as above. You can
... ...
@@ -248,7 +354,7 @@
248 354
     fingerprint in your Tor log files or in <tt>/var/lib/tor/fingerprint</tt>
249 355
     depending on your platform).
250 356
     </p>
251
-    
357
+
252 358
     <p>
253 359
     If you would like to learn more about our bridge
254 360
     design from a technical standpoint, please read the <a
... ...
@@ -265,5 +371,5 @@
265 371
   <!-- END SIDECOL -->
266 372
 </div>
267 373
 <!-- END CONTENT -->
268
-#include <foot.wmi>  
374
+#include <foot.wmi>
269 375
 
Browse code

add TODO comments to outdated docs

Nima Fatemi authored on28/10/2014 06:51:08 • Sebastian Hahn committed on28/10/2014 09:24:49
Showing1 changed files
... ...
@@ -3,6 +3,11 @@
3 3
 # Translation-Priority: 1-high
4 4
 
5 5
 #include "head.wmi" TITLE="Tor Project: Bridges" CHARSET="UTF-8"
6
+
7
+<!-- TODO: update screenshots -->
8
+<!-- TODO: rewrite "running a bridge" section -->
9
+<!-- TODO: add obfs4 how-tos -->
10
+
6 11
 <div id="content" class="clearfix">
7 12
   <div id="breadcrumbs">
8 13
     <a href="<page index>">Home &raquo; </a>
Browse code

Fix typo spotted by toralf

Sebastian Hahn authored on28/09/2014 13:03:27
Showing1 changed files
... ...
@@ -89,7 +89,7 @@
89 89
     detected they block the traffic flow.
90 90
     </p>
91 91
 
92
-    <p>To circumvent such sophisicated censorship Tor introduced
92
+    <p>To circumvent such sophisticated censorship Tor introduced
93 93
     <i>obfuscated bridges</i>. These bridges use special plugins
94 94
     called <i>pluggable transports</i> which obfuscate the traffic
95 95
     flow of Tor, making its detection harder.
Browse code

Bump Tor version in Bridge Relay installation instructions

Matthew Finkel authored on14/06/2014 09:06:27
Showing1 changed files
... ...
@@ -47,8 +47,8 @@
47 47
     FAQ about problems with running Tor properly</a> when you have issues.
48 48
     If you feel that the issue is clearly blocking, or you'd simply like to try
49 49
     because you're unsure or feeling adventurous, please read on. Ensure
50
-    that you're using the <a href="<page download/download>#Dev">latest 0.2.2.x or
51
-    0.2.3.x bundle for your platform</a>.
50
+    that you're using the <a href="<page download/download>#Dev">latest 0.2.3.x or
51
+    0.2.4.x bundle for your platform</a>.
52 52
     </p>
53 53
     
54 54
     <p>
Browse code

fix bad link from r25865

Roger Dingledine authored on25/12/2012 20:54:40
Showing1 changed files
... ...
@@ -95,9 +95,9 @@
95 95
     flow of Tor, making its detection harder.
96 96
 
97 97
     To connect to obfuscated bridges you need to use the <a
98
-    href=https://www.torproject.org/projects/obfsproxy.html.en#download>Obfproxy
98
+    href="<page projects/obfsproxy>#download">Obfsproxy
99 99
     Tor Browser Bundle</a>. The bundle includes some pre-configured
100
-    obfsproxy bridges and you can get more off <a
100
+    obfsproxy bridges and you can get more from <a
101 101
     href=https://bridges.torproject.org/?transport=obfs2>BridgeDB</a>
102 102
 
103 103
     <a id="Understanding"></a>
Browse code

Add pluggable transport information to docs/bridges.

George Kadianakis authored on06/11/2012 23:40:33
Showing1 changed files
... ...
@@ -13,6 +13,15 @@
13 13
     <a id="BridgeIntroduction"></a>
14 14
     <h2><a class="anchor" href="#BridgeIntroduction">Tor: Bridges</a></h2>
15 15
     <hr>
16
+
17
+    <p>
18
+    <img width="7%" height="7%" style="float: left;" src="$(IMGROOT)/icon-Obfsproxy.jpg">
19
+    <b>Tip:</b>
20
+    Having trouble connecting to Tor even when using bridges? You will
21
+    need to use <b>pluggable transports</b> and <b>obfuscated
22
+    bridges</b>. <a class="anchor" href="#PluggableTransports">Click
23
+    here for more information</a>.
24
+    </p>
16 25
     
17 26
     <p>
18 27
     Bridge relays (or "bridges" for short) are Tor relays that aren't listed in
... ...
@@ -70,10 +79,29 @@
70 79
     href="#FindingMore">other ways to find bridges</a> too.
71 80
     </p>
72 81
     
73
-    <a id="Understanding"></a>
74
-    <h2><a class="anchor" href="#Understanding">Understanding bridges</a></h2>
82
+    <a id="PluggableTransports"></a>
83
+    <h2><a class="anchor" href="#PluggableTransports">Obfuscated Bridges and Pluggable Transports</a></h2>
75 84
     <hr>
76 85
     
86
+    <p> Lately, censors have found ways to block Tor even when clients
87
+    are using bridges. They usually do this by installing boxes in
88
+    ISPs that peek at network traffic and detect Tor; when Tor is
89
+    detected they block the traffic flow.
90
+    </p>
91
+
92
+    <p>To circumvent such sophisicated censorship Tor introduced
93
+    <i>obfuscated bridges</i>. These bridges use special plugins
94
+    called <i>pluggable transports</i> which obfuscate the traffic
95
+    flow of Tor, making its detection harder.
96
+
97
+    To connect to obfuscated bridges you need to use the <a
98
+    href=https://www.torproject.org/projects/obfsproxy.html.en#download>Obfproxy
99
+    Tor Browser Bundle</a>. The bundle includes some pre-configured
100
+    obfsproxy bridges and you can get more off <a
101
+    href=https://bridges.torproject.org/?transport=obfs2>BridgeDB</a>
102
+
103
+    <a id="Understanding"></a>
104
+    <h2><a class="anchor" href="#Understanding">Understanding bridges</a></h2><hr>
77 105
     <p>
78 106
     As an example, you'll get a bridge entry that looks like the
79 107
     following:
... ...
@@ -90,8 +118,23 @@
90 118
     The second element is the port: <tt>'443'</tt><br>
91 119
     The third element, the fingerprint, is optional:
92 120
     <tt>'4352e58420e68f5e40bf7c74faddccd9d1349413'</tt><br>
121
+
122
+    <p>
123
+    <img width="7%" height="7%" style="vertical-align:middle" src="$(IMGROOT)/icon-Obfsproxy.jpg">
124
+         <span><b>Pluggable transports tip:</b></span>
93 125
     </p>
94
-    
126
+    <p>
127
+    If your bridge line looks like this:
128
+    <pre><samp>
129
+    bridge obfs2 141.201.27.48:420 4352e58420e68f5e40bf7c74faddccd9d1349413
130
+    </samp>
131
+    </pre>
132
+
133
+    The second element is the name of the pluggable transport
134
+    technology used by the bridge. For example, in the case above, the
135
+    bridge is using the <i>obfs2</i> pluggable transport.
136
+    </p>
137
+
95 138
     <a id="UsingBridges"></a>
96 139
     <h2><a class="anchor" href="#UsingBridges">Using bridges with Tor and
97 140
     Vidalia</a></h2>
... ...
@@ -115,6 +158,21 @@
115 158
     to reach the Tor network, but if you only have one bridge and it goes
116 159
     down, you will be cut off from the Tor network.
117 160
     </p>
161
+
162
+    <p>
163
+    <img width="7%" height="7%" style="vertical-align:middle" src="$(IMGROOT)/icon-Obfsproxy.jpg">
164
+         <span><b>Pluggable transports tip:</b></span>
165
+    </p>
166
+    <p>
167
+
168
+    If you have managed to get hold of some obfuscated bridge
169
+    addresses, you should add them in Vidalia in the same fashion that
170
+    you add normal bridges. Just paste the bridge line into the "Add a
171
+    bridge" window:
172
+
173
+    <br><br>
174
+    <img src="$(IMGROOT)/vidalia_add_obfsbridge.png" alt="Add obfuscated bridge in Vidalia">
175
+    <br><br>
118 176
     
119 177
     <a id="FindingMore"></a>
120 178
     <h2><a class="anchor" href="#FindingMore">Finding more bridges for Tor</a></h2>
Browse code

implement ticket 6213.

Andrew Lewman authored on20/06/2012 20:25:52
Showing1 changed files
... ...
@@ -122,7 +122,7 @@
122 122
     
123 123
     <p>
124 124
     Another way to find public bridge addresses is to send mail to
125
-    bridges@torproject.org with the line "get bridges" by itself in the
125
+    bridges@bridges.torproject.org with the line "get bridges" by itself in the
126 126
     body of the mail. You'll need to send this request from a gmail
127 127
     account, though &mdash; otherwise we make it too easy for an attacker
128 128
     to make a lot of email addresses and learn about all the bridges.
Browse code

fix bridges spec link

Roger Dingledine authored on16/03/2012 20:21:54
Showing1 changed files
... ...
@@ -189,7 +189,7 @@
189 189
     <p>
190 190
     If you would like to learn more about our bridge
191 191
     design from a technical standpoint, please read the <a
192
-    href="<specblob>bridges-spec.txt">Tor bridges
192
+    href="<specblob>attic/bridges-spec.txt">Tor bridges
193 193
     specification</a>. If you're interested in running an unpublished bridge
194 194
     or other non-standard uses, please do read the specification.
195 195
     </p>
Browse code

bring the bridge explanation partway out of the stone age

Roger Dingledine authored on02/12/2011 08:52:49
Showing1 changed files
... ...
@@ -25,11 +25,7 @@
25 25
     <p>
26 26
     The addition of bridges to Tor is a step forward in the blocking
27 27
     resistance race. It is perfectly possible that even if your ISP filters
28
-    the Internet, you do not require a bridge to use Tor. Many filtering
29
-    programs look for unencrypted Tor directory requests to recognize that
30
-    you're using Tor, but Tor version 0.2.0.23-rc and later use encrypted
31
-    directory queries by default. This change means that most filtering
32
-    programs are now unable to recognize Tor connections. So you should try
28
+    the Internet, you do not require a bridge to use Tor. So you should try
33 29
     to use Tor without bridges first, since it might work.
34 30
     </p>
35 31
     
... ...
@@ -42,8 +38,8 @@
42 38
     FAQ about problems with running Tor properly</a> when you have issues.
43 39
     If you feel that the issue is clearly blocking, or you'd simply like to try
44 40
     because you're unsure or feeling adventurous, please read on. Ensure
45
-    that you're using the <a href="<page download/download>#Dev">latest 0.2.1.x or
46
-    0.2.2.x bundle for your platform</a>.
41
+    that you're using the <a href="<page download/download>#Dev">latest 0.2.2.x or
42
+    0.2.3.x bundle for your platform</a>.
47 43
     </p>
48 44
     
49 45
     <p>
... ...
@@ -207,3 +203,4 @@
207 203
 </div>
208 204
 <!-- END CONTENT -->
209 205
 #include <foot.wmi>  
206
+
Browse code

change our "should i be a relay or a bridge" answer, and link to it from the bridge page

Roger Dingledine authored on22/08/2011 03:36:47
Showing1 changed files
... ...
@@ -149,11 +149,12 @@
149 149
     <hr>
150 150
     
151 151
     <p>
152
-    If you want to help out and you can't run a <a href="<page
153
-    docs/tor-doc-relay>">normal Tor relay</a>, you should
154
-    run a bridge relay. You can configure it either way:
152
+    If you want to help out, you should <a href="<page
153
+    docs/faq>#RelayOrBridge">decide whether you want to run a normal Tor
154
+    relay or a bridge relay</a>. You can configure your bridge either
155
+    manually or graphically:
155 156
     <ul>
156
-    <li> manually <a href="<page docs/faq>#torrc">edit
157
+    <li>manually <a href="<page docs/faq>#torrc">edit
157 158
     your torrc file</a> to be just these four lines:<br>
158 159
     <pre><code>
159 160
     SocksPort 0
Browse code

bridge lines typically don't come with fingerprints anymore

Roger Dingledine authored on21/07/2011 06:11:03
Showing1 changed files
... ...
@@ -134,11 +134,11 @@
134 134
     </p>
135 135
     <pre>
136 136
     Here are your bridge relays:
137
-    
138
-     bridge 60.16.182.53:9001 c9111bd74a710c0d25dda6b35e181f1aa7911133
139
-     bridge 87.237.118.139:444 c18dde4804e8fcb48464341ca1375eb130453a39
140
-     bridge 60.63.97.221:443 ab5c849ed5896d53052e43966ee9aba2ff92fb82
141
-    
137
+
138
+     bridge 60.16.182.53:9001
139
+     bridge 87.237.118.139:444
140
+     bridge 60.63.97.221:443
141
+
142 142
     </pre>
143 143
     <p>
144 144
     Once you've received the email with bridge information, you can continue the Vidalia configuration steps outlined <a href="#UsingBridges">above</a>.
Browse code

HTTPS-ify links to media.tpo and archive.tpo

Robert Ransom authored on29/03/2011 23:17:50
Showing1 changed files
... ...
@@ -63,7 +63,7 @@
63 63
     your language?  Let us know!</p>
64 64
     
65 65
     <div class="center">
66
-    <p><video id="v1" src="http://media.torproject.org/video/2009-using-a-bridge-relay-to-access-tor.ogv" autobuffer="true" controls="controls"></video></p>
66
+    <p><video id="v1" src="https://media.torproject.org/video/2009-using-a-bridge-relay-to-access-tor.ogv" autobuffer="true" controls="controls"></video></p>
67 67
     </div>
68 68
     
69 69
     <p>
Browse code

Fix links that broke due to splitting the spec in its own repo

Sebastian Hahn authored on21/02/2011 23:10:53
Showing1 changed files
... ...
@@ -192,7 +192,7 @@
192 192
     <p>
193 193
     If you would like to learn more about our bridge
194 194
     design from a technical standpoint, please read the <a
195
-    href="<gitblob>doc/spec/bridges-spec.txt">Tor bridges
195
+    href="<specblob>bridges-spec.txt">Tor bridges
196 196
     specification</a>. If you're interested in running an unpublished bridge
197 197
     or other non-standard uses, please do read the specification.
198 198
     </p>
Browse code

change links to the #torrc faq entry, fixing two broken links in the process

Roger Dingledine authored on07/02/2011 09:06:17
Showing1 changed files
... ...
@@ -153,8 +153,7 @@
153 153
     docs/tor-doc-relay>">normal Tor relay</a>, you should
154 154
     run a bridge relay. You can configure it either way:
155 155
     <ul>
156
-    <li> manually <a
157
-    href="<wikifaq>#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
156
+    <li> manually <a href="<page docs/faq>#torrc">edit
158 157
     your torrc file</a> to be just these four lines:<br>
159 158
     <pre><code>
160 159
     SocksPort 0
Browse code

our bridges page was linking to the wrong faq entry

Roger Dingledine authored on04/02/2011 02:49:47
Showing1 changed files
... ...
@@ -170,7 +170,7 @@
170 170
     
171 171
     <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
172 172
     on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
173
-    href="<wikifaq>#Myfirewallonlyallowsafewoutgoingports.">some
173
+    href="<page docs/faq>#HowcanImakemyrelayaccessibletopeoplestuckbehindrestrictivefirewalls">some
174 174
     complex port forwarding</a>.
175 175
     </p>
176 176
     
Browse code

looks like we never set the keywords either

Roger Dingledine authored on27/10/2010 12:31:57
Showing1 changed files
... ...
@@ -1,5 +1,5 @@
1 1
 ## translation metadata
2
-# Revision: $Revision: 22432 $
2
+# Revision: $Revision$
3 3
 # Translation-Priority: 1-high
4 4
 
5 5
 #include "head.wmi" TITLE="Tor Project: Bridges" CHARSET="UTF-8"
Browse code

We decided to go with HTML in favor of XHTML.

Sebastian Hahn authored on10/10/2010 03:34:47
Showing1 changed files
... ...
@@ -12,7 +12,7 @@
12 12
   <div id="maincol"> 
13 13
     <a id="BridgeIntroduction"></a>
14 14
     <h2><a class="anchor" href="#BridgeIntroduction">Tor: Bridges</a></h2>
15
-    <hr />
15
+    <hr>
16 16
     
17 17
     <p>
18 18
     Bridge relays (or "bridges" for short) are Tor relays that aren't listed in
... ...
@@ -76,7 +76,7 @@
76 76
     
77 77
     <a id="Understanding"></a>
78 78
     <h2><a class="anchor" href="#Understanding">Understanding bridges</a></h2>
79
-    <hr />
79
+    <hr>
80 80
     
81 81
     <p>
82 82
     As an example, you'll get a bridge entry that looks like the
... ...
@@ -89,17 +89,17 @@
89 89
     
90 90
     <p>
91 91
     Understanding the components of a bridge line isn't strictly required
92
-    but may prove useful. You can skip this section if you'd like.<br />
93
-    The first element is the IP address: <tt>'141.201.27.48'</tt><br />
94
-    The second element is the port: <tt>'443'</tt><br />
92
+    but may prove useful. You can skip this section if you'd like.<br>
93
+    The first element is the IP address: <tt>'141.201.27.48'</tt><br>
94
+    The second element is the port: <tt>'443'</tt><br>
95 95
     The third element, the fingerprint, is optional:
96
-    <tt>'4352e58420e68f5e40bf7c74faddccd9d1349413'</tt><br />
96
+    <tt>'4352e58420e68f5e40bf7c74faddccd9d1349413'</tt><br>
97 97
     </p>
98 98
     
99 99
     <a id="UsingBridges"></a>
100 100
     <h2><a class="anchor" href="#UsingBridges">Using bridges with Tor and
101 101
     Vidalia</a></h2>
102
-    <hr />
102
+    <hr>
103 103
     
104 104
     <p>
105 105
     To use the example bridge address above, go to Vidalia's Network settings
... ...
@@ -109,9 +109,9 @@
109 109
     sign. Adding a bridge is pictured below:
110 110
     </p>
111 111
     
112
-    <br /><br />
113
-    <img src="$(IMGROOT)/vidalia-bridges.png" alt="Vidalia's Network settings page" />
114
-    <br /><br />
112
+    <br><br>
113
+    <img src="$(IMGROOT)/vidalia-bridges.png" alt="Vidalia's Network settings page">
114
+    <br><br>
115 115
     
116 116
     <p>
117 117
     You'll want to add as many bridge addresses as you know about, since
... ...
@@ -122,7 +122,7 @@
122 122
     
123 123
     <a id="FindingMore"></a>
124 124
     <h2><a class="anchor" href="#FindingMore">Finding more bridges for Tor</a></h2>
125
-    <hr />
125
+    <hr>
126 126
     
127 127
     <p>
128 128
     Another way to find public bridge addresses is to send mail to
... ...
@@ -146,7 +146,7 @@
146 146
     
147 147
     <a id="RunningABridge"></a>
148 148
     <h2><a class="anchor" href="#RunningABridge">Running a Tor Bridge</a></h2>
149
-    <hr />
149
+    <hr>
150 150
     
151 151
     <p>
152 152
     If you want to help out and you can't run a <a href="<page
... ...
@@ -155,16 +155,16 @@
155 155
     <ul>
156 156
     <li> manually <a
157 157
     href="<wikifaq>#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
158
-    your torrc file</a> to be just these four lines:<br />
158
+    your torrc file</a> to be just these four lines:<br>
159 159
     <pre><code>
160 160
     SocksPort 0
161 161
     ORPort 443
162 162
     BridgeRelay 1
163 163
     Exitpolicy reject *:*
164 164
     </code></pre></li>
165
-    <li><a href="<page docs/tor-doc-relay>">or using Vidalia</a>:<br />
165
+    <li><a href="<page docs/tor-doc-relay>">or using Vidalia</a>:<br>
166 166
     <img src="$(IMGROOT)/vidalia-bridges-setup.png" alt="Vidalia's Sharing
167
-    settings page" /></li>
167
+    settings page"></li>
168 168
     </ul>
169 169
     </p>
170 170
     
Browse code

fix a bunch of broken links to the wiki and faq. use our tags more uniformly.

Roger Dingledine authored on10/10/2010 01:35:02
Showing1 changed files
... ...
@@ -38,7 +38,7 @@
38 38
     reasons. The latest version of <a href="<page projects/torbrowser>">The
39 39
     Tor Browser Bundle</a> on Windows tries to give you better hints about
40 40
     why Tor is having problems connecting. You should also read <a
41
-    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#IinstalledTorandPolipobutitsnotworking.">the
41
+    href="<wikifaq>#IinstalledTorandPolipobutitsnotworking.">the
42 42
     FAQ about problems with running Tor properly</a> when you have issues.
43 43
     If you feel that the issue is clearly blocking, or you'd simply like to try
44 44
     because you're unsure or feeling adventurous, please read on. Ensure
... ...
@@ -154,7 +154,7 @@
154 154
     run a bridge relay. You can configure it either way:
155 155
     <ul>
156 156
     <li> manually <a
157
-    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
157
+    href="<wikifaq>#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
158 158
     your torrc file</a> to be just these four lines:<br />
159 159
     <pre><code>
160 160
     SocksPort 0
... ...
@@ -170,7 +170,7 @@
170 170
     
171 171
     <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
172 172
     on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
173
-    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Myfirewallonlyallowsafewoutgoingports.">some
173
+    href="<wikifaq>#Myfirewallonlyallowsafewoutgoingports.">some
174 174
     complex port forwarding</a>.
175 175
     </p>
176 176
     
Browse code

change all of the breadcrumbs from page home to page index.

Andrew Lewman authored on12/08/2010 17:17:47
Showing1 changed files
... ...
@@ -5,7 +5,7 @@
5 5
 #include "head.wmi" TITLE="Tor Project: Bridges" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8
-    <a href="<page home>">Home &raquo; </a>
8
+    <a href="<page index>">Home &raquo; </a>
9 9
     <a href="<page docs/documentation>">Documentation &raquo; </a>
10 10
     <a href="<page docs/bridges>">Bridges</a>
11 11
   </div>
Browse code

first cut of the new, shiny tor website as wml.

Andrew Lewman authored on09/07/2010 03:55:22
Showing1 changed files
1 1
new file mode 100644
... ...
@@ -0,0 +1,209 @@
1
+## translation metadata
2
+# Revision: $Revision: 22432 $
3
+# Translation-Priority: 1-high
4
+
5
+#include "head.wmi" TITLE="Tor Project: Bridges" CHARSET="UTF-8"
6
+<div id="content" class="clearfix">
7
+  <div id="breadcrumbs">
8
+    <a href="<page home>">Home &raquo; </a>
9
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10
+    <a href="<page docs/bridges>">Bridges</a>
11
+  </div>
12
+  <div id="maincol"> 
13
+    <a id="BridgeIntroduction"></a>
14
+    <h2><a class="anchor" href="#BridgeIntroduction">Tor: Bridges</a></h2>
15
+    <hr />
16
+    
17
+    <p>
18
+    Bridge relays (or "bridges" for short) are Tor relays that aren't listed in
19
+    the main Tor directory. Since there is no complete public list of them, even if
20
+    your ISP is filtering connections to all the known Tor relays, they probably
21
+    won't be able to block all the bridges. If you suspect your access to the
22
+    Tor network is being blocked, you may want to use the bridge feature of Tor.
23
+    </p>
24
+    
25
+    <p>
26
+    The addition of bridges to Tor is a step forward in the blocking
27
+    resistance race. It is perfectly possible that even if your ISP filters
28
+    the Internet, you do not require a bridge to use Tor. Many filtering
29
+    programs look for unencrypted Tor directory requests to recognize that
30
+    you're using Tor, but Tor version 0.2.0.23-rc and later use encrypted
31
+    directory queries by default. This change means that most filtering
32
+    programs are now unable to recognize Tor connections. So you should try
33
+    to use Tor without bridges first, since it might work.
34
+    </p>
35
+    
36
+    <p>
37
+    Note that it's also possible that Tor is non-functional for other
38
+    reasons. The latest version of <a href="<page projects/torbrowser>">The
39
+    Tor Browser Bundle</a> on Windows tries to give you better hints about
40
+    why Tor is having problems connecting. You should also read <a
41
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#IinstalledTorandPolipobutitsnotworking.">the
42
+    FAQ about problems with running Tor properly</a> when you have issues.
43
+    If you feel that the issue is clearly blocking, or you'd simply like to try
44
+    because you're unsure or feeling adventurous, please read on. Ensure
45
+    that you're using the <a href="<page download/download>#Dev">latest 0.2.1.x or
46
+    0.2.2.x bundle for your platform</a>.
47
+    </p>
48
+    
49
+    <p>
50
+    To use a bridge, you'll need to locate one. Furthermore, you'll need to
51
+    configure Tor with whatever bridge address you intend to use. You'll do this
52
+    with Vidalia, the Tor controller.
53
+    If your Internet connection requires the use of a proxy, you'll probably
54
+    need to configure Vidalia to do so first. If you don't think you need
55
+    to configure a proxy for your Internet connection, you probably don't.
56
+    Give it a try and if you have issues, ask us for help.
57
+    </p>
58
+    
59
+    <p>Freedom House has produced a video on how to get and use Tor bridges.
60
+    If you don't see a video below, view it at <a
61
+    href="http://www.youtube.com/thetorproject">Youtube:
62
+    Freedom4Internet</a> Know of a better video, or one translated into
63
+    your language?  Let us know!</p>
64
+    
65
+    <div class="center">
66
+    <p><video id="v1" src="http://media.torproject.org/video/2009-using-a-bridge-relay-to-access-tor.ogv" autobuffer="true" controls="controls"></video></p>
67
+    </div>
68
+    
69
+    <p>
70
+    At the moment, you can get a bridge by visiting
71
+    <a href="https://bridges.torproject.org/">https://bridges.torproject.org/</a>
72
+    with your web browser. If this page is filtered for you, and you
73
+    don't have any other proxies or ways to reach it, there are <a
74
+    href="#FindingMore">other ways to find bridges</a> too.
75
+    </p>
76
+    
77
+    <a id="Understanding"></a>
78
+    <h2><a class="anchor" href="#Understanding">Understanding bridges</a></h2>
79
+    <hr />
80
+    
81
+    <p>
82
+    As an example, you'll get a bridge entry that looks like the
83
+    following:
84
+    </p>
85
+    <pre><samp>
86
+    bridge 141.201.27.48:443 4352e58420e68f5e40bf7c74faddccd9d1349413
87
+    </samp>
88
+    </pre>
89
+    
90
+    <p>
91
+    Understanding the components of a bridge line isn't strictly required
92
+    but may prove useful. You can skip this section if you'd like.<br />
93
+    The first element is the IP address: <tt>'141.201.27.48'</tt><br />
94
+    The second element is the port: <tt>'443'</tt><br />
95
+    The third element, the fingerprint, is optional:
96
+    <tt>'4352e58420e68f5e40bf7c74faddccd9d1349413'</tt><br />
97
+    </p>
98
+    
99
+    <a id="UsingBridges"></a>
100
+    <h2><a class="anchor" href="#UsingBridges">Using bridges with Tor and
101
+    Vidalia</a></h2>
102
+    <hr />
103
+    
104
+    <p>
105
+    To use the example bridge address above, go to Vidalia's Network settings
106
+    page, and click "My ISP blocks connections to the Tor network".  Add each
107
+    bridge address one at a time in the Vidalia Network settings page,
108
+    by pasting it into the "Add a Bridge" window and then clicking the "+"
109
+    sign. Adding a bridge is pictured below:
110
+    </p>
111
+    
112
+    <br /><br />
113
+    <img src="$(IMGROOT)/vidalia-bridges.png" alt="Vidalia's Network settings page" />
114
+    <br /><br />
115
+    
116
+    <p>
117
+    You'll want to add as many bridge addresses as you know about, since
118
+    additional bridges will increase reliability. One bridge should be enough
119
+    to reach the Tor network, but if you only have one bridge and it goes
120
+    down, you will be cut off from the Tor network.
121
+    </p>
122
+    
123
+    <a id="FindingMore"></a>
124
+    <h2><a class="anchor" href="#FindingMore">Finding more bridges for Tor</a></h2>
125
+    <hr />
126
+    
127
+    <p>
128
+    Another way to find public bridge addresses is to send mail to
129
+    bridges@torproject.org with the line "get bridges" by itself in the
130
+    body of the mail. You'll need to send this request from a gmail
131
+    account, though &mdash; otherwise we make it too easy for an attacker
132
+    to make a lot of email addresses and learn about all the bridges.
133
+    Almost instantly, you'll receive a reply that includes:
134
+    </p>
135
+    <pre>
136
+    Here are your bridge relays:
137
+    
138
+     bridge 60.16.182.53:9001 c9111bd74a710c0d25dda6b35e181f1aa7911133
139
+     bridge 87.237.118.139:444 c18dde4804e8fcb48464341ca1375eb130453a39
140
+     bridge 60.63.97.221:443 ab5c849ed5896d53052e43966ee9aba2ff92fb82
141
+    
142
+    </pre>
143
+    <p>
144
+    Once you've received the email with bridge information, you can continue the Vidalia configuration steps outlined <a href="#UsingBridges">above</a>.
145
+    </p>
146
+    
147
+    <a id="RunningABridge"></a>
148
+    <h2><a class="anchor" href="#RunningABridge">Running a Tor Bridge</a></h2>
149
+    <hr />
150
+    
151
+    <p>
152
+    If you want to help out and you can't run a <a href="<page
153
+    docs/tor-doc-relay>">normal Tor relay</a>, you should
154
+    run a bridge relay. You can configure it either way:
155
+    <ul>
156
+    <li> manually <a
157
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
158
+    your torrc file</a> to be just these four lines:<br />
159
+    <pre><code>
160
+    SocksPort 0
161
+    ORPort 443
162
+    BridgeRelay 1
163
+    Exitpolicy reject *:*
164
+    </code></pre></li>
165
+    <li><a href="<page docs/tor-doc-relay>">or using Vidalia</a>:<br />
166
+    <img src="$(IMGROOT)/vidalia-bridges-setup.png" alt="Vidalia's Sharing
167
+    settings page" /></li>
168
+    </ul>
169
+    </p>
170
+    
171
+    <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
172
+    on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
173
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Myfirewallonlyallowsafewoutgoingports.">some
174
+    complex port forwarding</a>.
175
+    </p>
176
+    
177
+    <p>
178
+    When configured as a bridge, your server will <b>not</b> appear in the public
179
+    Tor network.
180
+    </p>
181
+    
182
+    <p>
183
+    Your bridge relay will automatically publish its address to the bridge
184
+    authority, which will give it out via https or email as above. You can
185
+    also tell a user about your bridge directly: if you're using Vidalia,
186
+    you can copy-and-paste the bridge address from the Settings window. If
187
+    you're on Linux or BSD, you can construct the bridge address manually
188
+    using the <a href="#Understanding">format above</a> (you can find the
189
+    fingerprint in your Tor log files or in <tt>/var/lib/tor/fingerprint</tt>
190
+    depending on your platform).
191
+    </p>
192
+    
193
+    <p>
194
+    If you would like to learn more about our bridge
195
+    design from a technical standpoint, please read the <a
196
+    href="<gitblob>doc/spec/bridges-spec.txt">Tor bridges
197
+    specification</a>. If you're interested in running an unpublished bridge
198
+    or other non-standard uses, please do read the specification.
199
+    </p>
200
+  </div>
201
+  <!-- END MAINCOL -->
202
+  <div id = "sidecol">
203
+#include "side.wmi"
204
+#include "info.wmi"
205
+  </div>
206
+  <!-- END SIDECOL -->
207
+</div>
208
+<!-- END CONTENT -->
209
+#include <foot.wmi>