Browse code

Transferred all TBB FAQs from the wiki to the faq.wml

Matt Pagan authored on 13/01/2014 21:15:12
Showing 2 changed files
1 1
deleted file mode 100644
... ...
@@ -1,317 +0,0 @@
1
-## translation metadata
2
-# Revision: $Revision: 25929 $
3
-# Translation-Priority: 2-medium
4
-
5
-#include "head.wmi" TITLE="Tor Project: Tor Browser FAQ" 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/faq-torbrowser>">Tor Browser FAQ</a>
11
-  </div>
12
-  <div id="maincol">
13
-    <!-- PUT CONTENT AFTER THIS TAG  -->
14
-    <h1>Tor Browser FAQ</h1>
15
-    <hr>
16
-    <h3>Questions</h3>
17
-    <ul>
18
-    <li><a href="#WhereDidVidaliaGo">Where did the world map (Vidalia) 
19
-    go?</a></li>
20
-    <li><a href="#DisableJS">How do I disable JavaScript?</a></li>
21
-    <li><a href="#VerifyDownload">How do I verify the download 
22
-    (sha256sums.txt)?</a></li>
23
-    <li><a href="#NewIdentityClosingTabs">Why does "New Identity" close 
24
-    all my open tabs?</a></li>
25
-    <li><a href="#ConfigureRelayOrBridge">How do I configure Tor as a relay 
26
-    or bridge?</a></li>
27
-    <li><a href="#Timestamps">Why are the file timestamps from 2000?</a></li>
28
-    <li><a href="#SourceCode">Where is the source code for the bundle? How do 
29
-    I verify a build?</a></li>
30
-    </ul>
31
-    <hr>
32
-
33
-    <a id="WhereDidVidaliaGo"></a>
34
-    <h3><a class="anchor" href="#WhereDidVidaliaGo">Where did the world map 
35
-    (Vidalia) go?</a></h3>
36
-
37
-    <p>Vidalia has been replaced with Tor Launcher, which is a Firefox 
38
-    extension that provides similar functionality. Unfortunately, circuit 
39
-    status reporting is still missing, but we are <a 
40
-    href="https://trac.torproject.org/projects/tor/ticket/8641">working 
41
-    on providing it</a>. </p>
42
-
43
-    <p>In the meantime, we are providing standalone Vidalia packages for 
44
-    people who still want the map. Windows and Linux versions are <a 
45
-    href="​https://people.torproject.org/~erinn/vidalia-standalone-bundles/">
46
-    available here</a>. 
47
-
48
-    <p>To use these packages, extract them, then run the startup script. 
49
-    On Windows, this is "Start Vidalia.exe". On Linux, it is start-vidalia. 
50
-    They can be placed in a different directory from TBB (and likely should 
51
-    be). </p>
52
-
53
-    <p>This Vidalia package will only run properly if Tor Browser has already 
54
-    been launched. You cannot start it before launching Tor Browser. </p>
55
-
56
-    <p>MacOS is still under development, but in the mean time you can modify 
57
-    your TBB 2.x to be a standalone Vidalia (and then use it after starting 
58
-    TBB 3.x) by opening your TBB 2.x vidalia.conf file in an editor and 
59
-    replacing its contents with just these lines:</p>
60
-
61
-    <pre>
62
-    [General]
63
-    LanguageCode=en
64
-
65
-    [Tor]
66
-    ControlPort=9151
67
-    TorExecutable=.
68
-    Torrc=.
69
-    DataDirectory=.
70
-    AuthenticationMethod=cookie
71
-    </pre> 
72
-
73
-    <hr>
74
-
75
-    <a id="DisableJS"></a>
76
-    <h3><a class="anchor" href="#DisableJS">How do I disable JavaScript?</a>
77
-    </h3>
78
-
79
-    <p>Alas, Mozilla decided to get rid of the config checkbox for JavaScript 
80
-    from earlier Firefox versions. And since TBB 3.5 is based on Firefox 24 
81
-    (FF17 is unmaintained), that means TBB 3.5 doesn't have the config 
82
-    checkbox anymore either, which is unfortunate.</p>
83
-
84
-    <p>The simplest way to disable JavaScript in TBB 3.5 is to click on the 
85
-    Noscript "S" (between the green onion and the address bar), and select 
86
-    "Forbid scripts globally". Note that vanilla NoScript actually whitelists 
87
-    several domains even when you try to disable scripts globally, whereas 
88
-    Tor Browser's NoScript configuration disables all of them. </p>
89
-
90
-    <p>The more klunky way to disable JavaScript is to go to about:config, 
91
-    find javascript.enabled, and set it to false.</p>
92
-
93
-    <p>There is also a very simple addon available at addons.mozilla.org
94
-    called QuickJS, which provides a toolbar toggle for the javascript.enabled
95
-    about:config control. There are no configuration options for the addon, 
96
-    it just switches the javascript.enabled entry between true and false and 
97
-    provides a button for it. </p>
98
-
99
-    <p>If you want to be extra safe, use both the about:config setting and 
100
-    NoScript. </p>
101
-
102
-    <p>As for whether you should disable it or leave it enabled, that's <a 
103
-    href="https://www.torproject.org/docs/faq#TBBJavaScriptEnabled">a 
104
-    tradeoff we leave to you</a>.</p>
105
-
106
-    <hr>
107
-
108
-    <a id="VerifyDownload"></a>
109
-    <h3><a class="anchor" href="#VerifyDownload">How do I verify the download
110
-    (sha256sums.txt)?</a></h3>
111
-
112
-    <p>You can still verify your Tor Browser download by downloading the 
113
-    signature file (.asc) along with your package and <a 
114
-    href="https://www.torproject.org/docs/verifying-signatures.html.en">
115
-    checking the GPG signature</a> as before. We now have an additional 
116
-    verification method that allows you to verify the build as well as 
117
-    the download.</p>
118
-
119
-    <ul>
120
-      <li>Download the Tor Browser package, the sha256sums.txt file, and the
121
-      sha256sums signature files. They can all be found in the same directory 
122
-      under <a href="https://www.torproject.org/dist/torbrowser/">
123
-      https://www.torproject.org/dist/torbrowser/</a>, for example in 3.5 
124
-      for TBB 3.5.</li>
125
-      <li>Retrieve the signers' GPG keys. This can be done from the command 
126
-      line by entering something like 
127
-      <pre>gpg --keyserver keys.mozilla.org --recv-keys 0x29846B3C683686CC</pre>
128
-      (This will bring you developer Mike Perry's public key. Other 
129
-      developers' key IDs can be found on
130
-      <a href="https://www.torproject.org/docs/signing-keys.html.en">this 
131
-      page</a>.)</li>
132
-      <li>Verify the sha256sums.txt file by executing this command:
133
-      <pre>gpg --verify &lt;NAME OF THE SIGNATURE FILE&gt;.asc sha256sums.txt</pre></li>
134
-      <li>You should see a message like "Good signature from &lt;DEVELOPER 
135
-      NAME&gt;". If you don't, there is a problem. Try these steps again.</li>
136
-      <li>Now you can take the sha256sum of the Tor Browser package. On 
137
-      Windows you can use the <a href="http://md5deep.sourceforge.net/">
138
-      hashdeep utility</a> and run
139
-      <pre>C:\location\where\you\saved\hashdeep -c sha256sum &lt;TOR BROWSER FILE NAME&gt;.exe</pre>
140
-      On Mac or Linux you can run <pre>sha256sum &lt;TOR BROWSER FILE NAME&gt;.zip</pre> or <pre>sha256sum &lt;TOR BROWSER FILE NAME&gt;.tar.gz</pre> without having to download a utility.</li>
141
-      <li>You will see a string of letters and numbers.</li>
142
-      <li>Open sha256sums.txt in a text editor.</li>
143
-      <li>Locate the name of the Tor Browser file you downloaded.</li>
144
-      <li>Compare the string of letters and numbers to the left of your
145
-      filename with the string of letters and numbers that appeared 
146
-      on your command line. If they match, you've successfully verified the 
147
-      build.</li> 
148
-    </ul>
149
-
150
-    <p><a href="https://github.com/isislovecruft/scripts/blob/master/verify-gitian-builder-signatures">
151
-    Scripts</a> to <a 
152
-    href="http://tor.stackexchange.com/questions/648/how-to-verify-tor-browser-bundle-tbb-3-x">automate
153
-    </a> these steps have been written, but to use them you will need to 
154
-    modify them yourself with the latest Tor Browser Bundle filename.</p>
155
-
156
-    <hr>
157
-
158
-    <a id="PluggableTransports"></a>
159
-    <h3><a class="anchor" href="#PluggableTransports">How do I use pluggable transports?</a></h3>
160
-
161
-    <p>
162
-    For now, the Pluggable Transports-capable TBB is still a separate 
163
-    unofficial package. Download them <a 
164
-    href="https://people.torproject.org/~dcf/pt-bundle/3.5-pt20131217/">
165
-    here</a>. We hope to have combined packages available in a beta soon.
166
-    </p>
167
-
168
-    <p>
169
-    The separate Pluggable Transports-capable TBB is different from the 
170
-    Pluggable Transports bundles that have been released in the past. 
171
-    They include the programs necessary to use obfsproxy and flash proxy, 
172
-    but the pluggable transports are not enabled by default. You must 
173
-    enable them manually by adding Bridge lines to the torrc file. 
174
-    (Please see ticket <a 
175
-    href="https://trac.torproject.org/projects/tor/ticket/10418">#10418</a> 
176
-    for how we hope to make it easier to do in the future.)
177
-    </p>
178
-
179
-    <p>
180
-    To enable <b>obfsproxy</b>, edit the file called Data/Tor/torrc inside the 
181
-    bundle and add the lines: 
182
-    </p>
183
-
184
-    <pre>
185
-Bridge obfs3 83.212.101.2:42782 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
186
-Bridge obfs3 83.212.101.2:443 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
187
-Bridge obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9
188
-Bridge obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9
189
-Bridge obfs3 209.141.36.236:45496
190
-Bridge obfs3 208.79.90.242:35658
191
-Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD
192
-Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E
193
-Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80
194
-Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41
195
-Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35
196
-Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496
197
-Bridge obfs2 83.212.101.2:45235 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
198
-    </pre>
199
-    <p>
200
-    To enable <b>flash proxy</b>, edit the file called Data/Tor/torrc inside the 
201
-    bundle and add the lines: 
202
-    </p>
203
-    <pre>
204
-LearnCircuitBuildTimeout 0
205
-CircuitBuildTimeout 60
206
-Bridge flashproxy 0.0.1.0:1
207
-    </pre>
208
-
209
-    <hr>
210
-
211
-    <a id="NewIdentityClosingTabs"></a>
212
-    <h3><a class="anchor" href="#NewIdentityClosingTabs">Why does "New 
213
-    Identity" close all my open tabs?</a></h3>
214
-
215
-    <p>
216
-    That's actually a feature, since it's discarding your application-level 
217
-    browser data too. But it sure is a surprising feature, for people who 
218
-    are used to Vidalia's "new identity" behavior.
219
-    </p>
220
-
221
-    <p>
222
-    We're working on ways to make the behavior less surprising, e.g. a popup 
223
-    warning or auto restoring tabs. See ticket <a 
224
-    href="https://trac.torproject.org/projects/tor/ticket/9906">#9906</a> and 
225
-    ticket <a href="https://trac.torproject.org/projects/tor/ticket/10400">
226
-    #10400</a> to follow progress there.
227
-    </p>
228
-
229
-    <p>
230
-    In the mean time, you can get Vidalia's old "newnym" functionality by 
231
-    attaching a Vidalia to your TBB3.x. See the instructions above.
232
-    </p>
233
-
234
-    <hr>
235
-
236
-    <a id="ConfigureRelayOrBridge"></a>
237
-    <h3><a class="anchor" href="#ConfigureRelayOrBridge">How do I configure Tor as a relay or bridge?</a></h3>
238
-
239
-    <p>
240
-    You've got three options. 
241
-    </p>
242
-
243
-    <p>
244
-    First (best option), if you're on Linux, you can install the system 
245
-    Tor package (e.g. apt-get install tor) and then set it up to be a relay 
246
-    (<a href="https://www.torproject.org/docs/tor-relay-debian">instructions</a>). 
247
-    You can then use TBB independent of that.
248
-    </p>
249
-
250
-    <p>
251
-    Second (simpler option), if you're on Windows, you can fetch the separate 
252
-    "Vidalia relay bundle" or "Vidalia bridge bundle" from the download page 
253
-    and then use that (again you can use TBB independent of it). 
254
-    </p>
255
-
256
-    <p>
257
-    Third (complex option), you can either hook your Vidalia up to TBB (as 
258
-    described in the FAQ above) or edit your torrc file (in Data/Tor/torrc) 
259
-    directly to add the following lines: 
260
-    </p>
261
-    <pre>
262
-    ORPort 443
263
-    Exitpolicy reject *:*
264
-    BridgeRelay 1  # only add this line if you want to be a bridge
265
-    </pre>
266
-    <p>
267
-    If you've installed <a 
268
-    href="https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en#instructions">Obfsproxy</a>, 
269
-    you'll need to add one more line:
270
-    </p>
271
-    <pre>
272
-    ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
273
-    </pre>
274
-    <p>
275
-    This third option is pretty klunky right now; see e.g. <a 
276
-    href="https://trac.torproject.org/projects/tor/ticket/10449">this bug</a>; 
277
-    but we're hoping it will become an easy option in the future. 
278
-    </p>
279
-
280
-    <hr>
281
-
282
-    <a id="Timestamps"></a>
283
-    <h3><a class="anchor" href="#Timestamps">Why are the file timestamps 
284
-    from 2000?</a></h3>
285
-
286
-    <p>One of the huge new features in TBB 3.x is the "deterministic build" 
287
-    process, which allows many people to build the Tor Browser Bundle and 
288
-    verify that they all make exactly the same package. See Mike's <a 
289
-    href="https://blog.torproject.org/blog/deterministic-builds-part-one-cyberwar-and-global-compromise">first 
290
-    blog</a> post for the motivation, and his <a 
291
-    href="https://blog.torproject.org/blog/deterministic-builds-part-two-technical-details">second
292
-    blog post</a> for the technical details of how we do it. 
293
-    </p>
294
-
295
-    <p>Part of creating identical builds is having everybody use the same 
296
-    timestamp. Mike picked the beginning of 2000 for that time. The reason 
297
-    you might see 7pm in 1999 is because of time zones. </p>
298
-
299
-    <hr>
300
-
301
-    <a id="SourceCode"></a>
302
-    <h3><a class="anchor" href="#SourceCode">Where is the source code for the bundle? How do I verify a build?</a></h3>
303
-
304
-    <p>
305
-    Start with <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">https://gitweb.torproject.org/builders/tor-browser-bundle.git</a> and <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build">https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build</a>.
306
-    </p>
307
-
308
-  </div>
309
-  <!-- END MAINCOL -->
310
-  <div id = "sidecol">
311
-#include "side.wmi"
312
-#include "info.wmi"
313
-  </div>
314
-  <!-- END SIDECOL -->
315
-</div>
316
-<!-- END CONTENT -->
317
-#include <foot.wmi>
... ...
@@ -95,6 +95,18 @@ tells
95 95
     <li><a href="#WarningsAboutSOCKSandDNSInformationLeaks">I keep seeing 
96 96
     these warnings about SOCKS and DNS information leaks. Should I 
97 97
     worry?</a></li>
98
+    <li><a href="#WhereDidVidaliaGo">Where did the world map (Vidalia) 
99
+    go?</a></li>
100
+    <li><a href="#DisableJS">How do I disable JavaScript?</a></li>
101
+    <li><a href="#VerifyDownload">How do I verify the download 
102
+    (sha256sums.txt)?</a></li>
103
+    <li><a href="#NewIdentityClosingTabs">Why does "New Identity" close 
104
+    all my open tabs?</a></li>
105
+    <li><a href="#ConfigureRelayOrBridge">How do I configure Tor as a relay 
106
+    or bridge?</a></li>
107
+    <li><a href="#Timestamps">Why are the file timestamps from 2000?</a></li>
108
+    <li><a href="#SourceCode">Where is the source code for the bundle? How do 
109
+    I verify a build?</a></li>
98 110
     </ul>
99 111
 
100 112
     <p>Advanced Tor usage:</p>
... ...
@@ -1510,6 +1522,284 @@ When your application uses SOCKS 4 or SOCKS 5 to give Tor an IP address, Tor gue
1510 1522
  If you think that you applied one of the solutions properly but still experience DNS leaks please verify there is no third-party application using DNS independently of Tor. Please see <a href="#AmITotallyAnonymous">the FAQ entry on whether you're really absolutely anonymous using Tor</a> for some examples. 
1511 1523
 </p>
1512 1524
 
1525
+    <hr>
1526
+
1527
+    <a id="WhereDidVidaliaGo"></a>
1528
+    <h3><a class="anchor" href="#WhereDidVidaliaGo">Where did the world map 
1529
+    (Vidalia) go?</a></h3>
1530
+
1531
+    <p>Vidalia has been replaced with Tor Launcher, which is a Firefox 
1532
+    extension that provides similar functionality. Unfortunately, circuit 
1533
+    status reporting is still missing, but we are <a 
1534
+    href="https://trac.torproject.org/projects/tor/ticket/8641">working 
1535
+    on providing it</a>. </p>
1536
+
1537
+    <p>In the meantime, we are providing standalone Vidalia packages for 
1538
+    people who still want the map. Windows and Linux versions are <a 
1539
+    href="​https://people.torproject.org/~erinn/vidalia-standalone-bundles/">
1540
+    available here</a>. 
1541
+
1542
+    <p>To use these packages, extract them, then run the startup script. 
1543
+    On Windows, this is "Start Vidalia.exe". On Linux, it is start-vidalia. 
1544
+    They can be placed in a different directory from TBB (and likely should 
1545
+    be). </p>
1546
+
1547
+    <p>This Vidalia package will only run properly if Tor Browser has already 
1548
+    been launched. You cannot start it before launching Tor Browser. </p>
1549
+
1550
+    <p>MacOS is still under development, but in the mean time you can modify 
1551
+    your TBB 2.x to be a standalone Vidalia (and then use it after starting 
1552
+    TBB 3.x) by opening your TBB 2.x vidalia.conf file in an editor and 
1553
+    replacing its contents with just these lines:</p>
1554
+
1555
+    <pre>
1556
+    [General]
1557
+    LanguageCode=en
1558
+
1559
+    [Tor]
1560
+    ControlPort=9151
1561
+    TorExecutable=.
1562
+    Torrc=.
1563
+    DataDirectory=.
1564
+    AuthenticationMethod=cookie
1565
+    </pre> 
1566
+
1567
+    <hr>
1568
+
1569
+    <a id="DisableJS"></a>
1570
+    <h3><a class="anchor" href="#DisableJS">How do I disable JavaScript?</a>
1571
+    </h3>
1572
+
1573
+    <p>Alas, Mozilla decided to get rid of the config checkbox for JavaScript 
1574
+    from earlier Firefox versions. And since TBB 3.5 is based on Firefox 24 
1575
+    (FF17 is unmaintained), that means TBB 3.5 doesn't have the config 
1576
+    checkbox anymore either, which is unfortunate.</p>
1577
+
1578
+    <p>The simplest way to disable JavaScript in TBB 3.5 is to click on the 
1579
+    Noscript "S" (between the green onion and the address bar), and select 
1580
+    "Forbid scripts globally". Note that vanilla NoScript actually whitelists 
1581
+    several domains even when you try to disable scripts globally, whereas 
1582
+    Tor Browser's NoScript configuration disables all of them. </p>
1583
+
1584
+    <p>The more klunky way to disable JavaScript is to go to about:config, 
1585
+    find javascript.enabled, and set it to false.</p>
1586
+
1587
+    <p>There is also a very simple addon available at addons.mozilla.org
1588
+    called QuickJS, which provides a toolbar toggle for the javascript.enabled
1589
+    about:config control. There are no configuration options for the addon, 
1590
+    it just switches the javascript.enabled entry between true and false and 
1591
+    provides a button for it. </p>
1592
+
1593
+    <p>If you want to be extra safe, use both the about:config setting and 
1594
+    NoScript. </p>
1595
+
1596
+    <p>As for whether you should disable it or leave it enabled, that's <a 
1597
+    href="https://www.torproject.org/docs/faq#TBBJavaScriptEnabled">a 
1598
+    tradeoff we leave to you</a>.</p>
1599
+
1600
+    <hr>
1601
+
1602
+    <a id="VerifyDownload"></a>
1603
+    <h3><a class="anchor" href="#VerifyDownload">How do I verify the download
1604
+    (sha256sums.txt)?</a></h3>
1605
+
1606
+    <p>You can still verify your Tor Browser download by downloading the 
1607
+    signature file (.asc) along with your package and <a 
1608
+    href="https://www.torproject.org/docs/verifying-signatures.html.en">
1609
+    checking the GPG signature</a> as before. We now have an additional 
1610
+    verification method that allows you to verify the build as well as 
1611
+    the download.</p>
1612
+
1613
+    <ul>
1614
+      <li>Download the Tor Browser package, the sha256sums.txt file, and the
1615
+      sha256sums signature files. They can all be found in the same directory 
1616
+      under <a href="https://www.torproject.org/dist/torbrowser/">
1617
+      https://www.torproject.org/dist/torbrowser/</a>, for example in 3.5 
1618
+      for TBB 3.5.</li>
1619
+      <li>Retrieve the signers' GPG keys. This can be done from the command 
1620
+      line by entering something like 
1621
+      <pre>gpg --keyserver keys.mozilla.org --recv-keys 0x29846B3C683686CC</pre>
1622
+      (This will bring you developer Mike Perry's public key. Other 
1623
+      developers' key IDs can be found on
1624
+      <a href="https://www.torproject.org/docs/signing-keys.html.en">this 
1625
+      page</a>.)</li>
1626
+      <li>Verify the sha256sums.txt file by executing this command:
1627
+      <pre>gpg --verify &lt;NAME OF THE SIGNATURE FILE&gt;.asc sha256sums.txt</pre></li>
1628
+      <li>You should see a message like "Good signature from &lt;DEVELOPER 
1629
+      NAME&gt;". If you don't, there is a problem. Try these steps again.</li>
1630
+      <li>Now you can take the sha256sum of the Tor Browser package. On 
1631
+      Windows you can use the <a href="http://md5deep.sourceforge.net/">
1632
+      hashdeep utility</a> and run
1633
+      <pre>C:\location\where\you\saved\hashdeep -c sha256sum &lt;TOR BROWSER FILE NAME&gt;.exe</pre>
1634
+      On Mac or Linux you can run <pre>sha256sum &lt;TOR BROWSER FILE NAME&gt;.zip</pre> or <pre>sha256sum &lt;TOR BROWSER FILE NAME&gt;.tar.gz</pre> without having to download a utility.</li>
1635
+      <li>You will see a string of letters and numbers.</li>
1636
+      <li>Open sha256sums.txt in a text editor.</li>
1637
+      <li>Locate the name of the Tor Browser file you downloaded.</li>
1638
+      <li>Compare the string of letters and numbers to the left of your
1639
+      filename with the string of letters and numbers that appeared 
1640
+      on your command line. If they match, you've successfully verified the 
1641
+      build.</li> 
1642
+    </ul>
1643
+
1644
+    <p><a href="https://github.com/isislovecruft/scripts/blob/master/verify-gitian-builder-signatures">
1645
+    Scripts</a> to <a 
1646
+    href="http://tor.stackexchange.com/questions/648/how-to-verify-tor-browser-bundle-tbb-3-x">automate
1647
+    </a> these steps have been written, but to use them you will need to 
1648
+    modify them yourself with the latest Tor Browser Bundle filename.</p>
1649
+
1650
+    <hr>
1651
+
1652
+    <a id="PluggableTransports"></a>
1653
+    <h3><a class="anchor" href="#PluggableTransports">How do I use pluggable transports?</a></h3>
1654
+
1655
+    <p>
1656
+    For now, the Pluggable Transports-capable TBB is still a separate 
1657
+    unofficial package. Download them <a 
1658
+    href="https://people.torproject.org/~dcf/pt-bundle/3.5-pt20131217/">
1659
+    here</a>. We hope to have combined packages available in a beta soon.
1660
+    </p>
1661
+
1662
+    <p>
1663
+    The separate Pluggable Transports-capable TBB is different from the 
1664
+    Pluggable Transports bundles that have been released in the past. 
1665
+    They include the programs necessary to use obfsproxy and flash proxy, 
1666
+    but the pluggable transports are not enabled by default. You must 
1667
+    enable them manually by adding Bridge lines to the torrc file. 
1668
+    (Please see ticket <a 
1669
+    href="https://trac.torproject.org/projects/tor/ticket/10418">#10418</a> 
1670
+    for how we hope to make it easier to do in the future.)
1671
+    </p>
1672
+
1673
+    <p>
1674
+    To enable <b>obfsproxy</b>, edit the file called Data/Tor/torrc inside the 
1675
+    bundle and add the lines: 
1676
+    </p>
1677
+
1678
+    <pre>
1679
+Bridge obfs3 83.212.101.2:42782 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
1680
+Bridge obfs3 83.212.101.2:443 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
1681
+Bridge obfs3 169.229.59.74:31493 AF9F66B7B04F8FF6F32D455F05135250A16543C9
1682
+Bridge obfs3 169.229.59.75:46328 AF9F66B7B04F8FF6F32D455F05135250A16543C9
1683
+Bridge obfs3 209.141.36.236:45496
1684
+Bridge obfs3 208.79.90.242:35658
1685
+Bridge obfs3 109.105.109.163:38980 9D7259A696F7DAB073043B28114112A46D36CFFD
1686
+Bridge obfs3 109.105.109.163:47779 844B1F53FFD548C998F8D3B01B7E19FA07C3396E
1687
+Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80
1688
+Bridge obfs2 83.212.96.182:46602 6F058CBEF888EB20D1DEB9886909F1E812245D41
1689
+Bridge obfs2 70.182.182.109:54542 94C9E691688FAFDEC701A0788BD15BE8AD34ED35
1690
+Bridge obfs2 128.31.0.34:1051 CA7434F14A898C7D3427B8295A7F83446BC7F496
1691
+Bridge obfs2 83.212.101.2:45235 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
1692
+    </pre>
1693
+    <p>
1694
+    To enable <b>flash proxy</b>, edit the file called Data/Tor/torrc inside the 
1695
+    bundle and add the lines: 
1696
+    </p>
1697
+    <pre>
1698
+LearnCircuitBuildTimeout 0
1699
+CircuitBuildTimeout 60
1700
+Bridge flashproxy 0.0.1.0:1
1701
+    </pre>
1702
+
1703
+    <hr>
1704
+
1705
+    <a id="NewIdentityClosingTabs"></a>
1706
+    <h3><a class="anchor" href="#NewIdentityClosingTabs">Why does "New 
1707
+    Identity" close all my open tabs?</a></h3>
1708
+
1709
+    <p>
1710
+    That's actually a feature, since it's discarding your application-level 
1711
+    browser data too. But it sure is a surprising feature, for people who 
1712
+    are used to Vidalia's "new identity" behavior.
1713
+    </p>
1714
+
1715
+    <p>
1716
+    We're working on ways to make the behavior less surprising, e.g. a popup 
1717
+    warning or auto restoring tabs. See ticket <a 
1718
+    href="https://trac.torproject.org/projects/tor/ticket/9906">#9906</a> and 
1719
+    ticket <a href="https://trac.torproject.org/projects/tor/ticket/10400">
1720
+    #10400</a> to follow progress there.
1721
+    </p>
1722
+
1723
+    <p>
1724
+    In the mean time, you can get Vidalia's old "newnym" functionality by 
1725
+    attaching a Vidalia to your TBB3.x. See the instructions above.
1726
+    </p>
1727
+
1728
+    <hr>
1729
+
1730
+    <a id="ConfigureRelayOrBridge"></a>
1731
+    <h3><a class="anchor" href="#ConfigureRelayOrBridge">How do I configure Tor as a relay or bridge?</a></h3>
1732
+
1733
+    <p>
1734
+    You've got three options. 
1735
+    </p>
1736
+
1737
+    <p>
1738
+    First (best option), if you're on Linux, you can install the system 
1739
+    Tor package (e.g. apt-get install tor) and then set it up to be a relay 
1740
+    (<a href="https://www.torproject.org/docs/tor-relay-debian">instructions</a>). 
1741
+    You can then use TBB independent of that.
1742
+    </p>
1743
+
1744
+    <p>
1745
+    Second (simpler option), if you're on Windows, you can fetch the separate 
1746
+    "Vidalia relay bundle" or "Vidalia bridge bundle" from the download page 
1747
+    and then use that (again you can use TBB independent of it). 
1748
+    </p>
1749
+
1750
+    <p>
1751
+    Third (complex option), you can either hook your Vidalia up to TBB (as 
1752
+    described in the FAQ above) or edit your torrc file (in Data/Tor/torrc) 
1753
+    directly to add the following lines: 
1754
+    </p>
1755
+    <pre>
1756
+    ORPort 443
1757
+    Exitpolicy reject *:*
1758
+    BridgeRelay 1  # only add this line if you want to be a bridge
1759
+    </pre>
1760
+    <p>
1761
+    If you've installed <a 
1762
+    href="https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en#instructions">Obfsproxy</a>, 
1763
+    you'll need to add one more line:
1764
+    </p>
1765
+    <pre>
1766
+    ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed
1767
+    </pre>
1768
+    <p>
1769
+    This third option is pretty klunky right now; see e.g. <a 
1770
+    href="https://trac.torproject.org/projects/tor/ticket/10449">this bug</a>; 
1771
+    but we're hoping it will become an easy option in the future. 
1772
+    </p>
1773
+
1774
+    <hr>
1775
+
1776
+    <a id="Timestamps"></a>
1777
+    <h3><a class="anchor" href="#Timestamps">Why are the file timestamps 
1778
+    from 2000?</a></h3>
1779
+
1780
+    <p>One of the huge new features in TBB 3.x is the "deterministic build" 
1781
+    process, which allows many people to build the Tor Browser Bundle and 
1782
+    verify that they all make exactly the same package. See Mike's <a 
1783
+    href="https://blog.torproject.org/blog/deterministic-builds-part-one-cyberwar-and-global-compromise">first 
1784
+    blog</a> post for the motivation, and his <a 
1785
+    href="https://blog.torproject.org/blog/deterministic-builds-part-two-technical-details">second
1786
+    blog post</a> for the technical details of how we do it. 
1787
+    </p>
1788
+
1789
+    <p>Part of creating identical builds is having everybody use the same 
1790
+    timestamp. Mike picked the beginning of 2000 for that time. The reason 
1791
+    you might see 7pm in 1999 is because of time zones. </p>
1792
+
1793
+    <hr>
1794
+
1795
+    <a id="SourceCode"></a>
1796
+    <h3><a class="anchor" href="#SourceCode">Where is the source code for the bundle? How do I verify a build?</a></h3>
1797
+
1798
+    <p>
1799
+    Start with <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">https://gitweb.torproject.org/builders/tor-browser-bundle.git</a> and <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build">https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build</a>.
1800
+    </p>
1801
+
1802
+
1513 1803
 <hr>
1514 1804
 
1515 1805
 <a id="torrc"></a>