tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 2-medium
4) 
5) #include "head.wmi" TITLE="Tor Project: Verifying Signatures" 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/verifying-signatures>">Verifying Signatures</a>
10)   </div>

11)   <div id="maincol">

12) 

13) <section class="accordion">
14) <!--
15)   This section uses a CSS accordion to hide and show topics.
16)   Styles are defined at the bottom of layout.css.
17) -->
18)  <div>
19)    <input id="ac-0" name="accordion-0" type="checkbox" checked />
20)    <label for="ac-0">

21)     <h1><a name="TOC">How to verify signatures of packages</a></h1>

22)     <hr>

23)    </label>
24)    <article class="ac-small">
25) <!-- TOC -->
26)     <div class="nav img-shadow">
27)     <div class="sidenav-sub">
28)     <ul>
29)       <li><a href="#Why-verify-signature">Always verify downloads</a></li>

30)       <li><a href="#ImportKey">Import Tor's signing key</a></li>
31)       <li><a href="#VerifySignature">Verify OpenPGP signatures</a></li>
32)       <li><a href="#ChecksumVerification">Verify checksums</a></li>
33)       <li><a href="#MARVerification">MAR verification</a></li>
34)       <li><a href="#Troubleshooting">Troubleshooting</a></li>

35)       <li><a href="#Scripts">Scripts</a></li>
36)     </ul>
37)     </div>
38)     </div>

39) 

40) <!-- Intro -->

41)     <p>Digital signature is a process ensuring that a certain package was
42)     generated by its developers and has not been tampered with. Below we explain
43)     why it is important and how to verify that the Tor program you download is
44)     the one we have created and has not been modified by some attacker.</p>
45) 

46)     <p>If you want to learn more about how it works see<br/>

47)     <a href="https://en.wikipedia.org/wiki/Digital_signature">
48)     https://en.wikipedia.org/wiki/Digital_signature</a>.</p>
49) 

50)     <p class="hint">(Click on each headline to show or hide the section.)</p>

51)   </article>
52)  </div>

53) 

54) <!-- Motivation -->
55)  <div>
56)    <input id="ac-1" name="accordion-1" type="checkbox" />
57)    <label for="ac-1">
58)     <a class="nav" title="link here" href="#Why-verify-signature">&#9668;</a>

59)     <h3><a name="Why-verify-signature">Always verify the signature of
60)         downloaded files</a></h3>

61)     <hr>

62)     <p>
63)     How do you know that the Tor program you have is really the one we made?

64)     Digital signatures ensure that the package you are downloading was created
65)     by our <a href="<>page about/corepeople>">developers</a>. It uses a
66)     cryptographic mechanism to ensure that the software package that you have
67)     just downloaded is authentic.
68)     <span class="hint">(click to toggle)</span></p>

69)    </label>
70)    <article class="ac-small">
71) 

72)     <p>

73)     For many Tor users it is important to verify that the Tor software is
74)     authentic as they have very real adversaries who might try to give them a
75)     fake version of Tor.

76)     </p>

77) 

78)     <p>

79)     If the Tor package has been modified by some attacker it is not safe to use
80)     it. It doesn't matter how secure and anonymous Tor is if you're not running
81)     the real Tor.

82)     </p>

83) 

84)     <p>
85)     Before you go ahead and download something, there are a few extra steps you
86)     should take to make sure you have downloaded an authentic version of Tor.
87)     </p>

88) 
89)     <h4>Always download Tor from torproject.org</h4>
90) 

91)     <p>
92)     There are a variety of attacks that can be used to make you download a fake

93)     version of Tor. For example, an attacker could trick you into thinking some
94)     other website is a great place to download Tor. You should always download
95)     Tor from
96)     <a href="https://www.torproject.org"><b>https</b>://www.torproject.org/</a>.

97)     </p>

98) 

99)     <h4>Always make sure you are browsing over https</h4>
100) 

101)     <p>

102)     <a href="https://www.torproject.org">https://www.torproject.org/</a> uses
103)     https. Https is the secure version of the http protocol which uses
104)     encryption and authentication between your browser and the website.
105)     This makes it much harder for the attacker to modify your download. But
106)     it's not perfect. Some places in the world block the Tor website, making
107)     users to download Tor <a href="<page docs/faq>#GetTor">somewhere else</a>.

108)     </p>

109) 

110)     <p>
111)     Large companies sometimes force employees to use a modified browser,

112)     so the company can listen in on all their browsing. We've even
113)     <a href="https://blog.torproject.org/blog/diginotar-debacle-and-what-you-should-do-about-it">seen</a>

114)     attackers who have the ability to trick your browser into thinking

115)     you're talking to the Tor website with https when you're not.
116)     </p>

117) 

118)     <h4>Always verify signatures of packages you have downloaded</h4>
119) 

120)     <p>
121)     Some software sites list
122)     <a href="https://en.wikipedia.org/wiki/Cryptographic_hash_function">sha1

123)     hashes</a> alongside the software on their website, so users can
124)     verify that they downloaded the file without any errors. These
125)     "checksums" help you answer the question "Did I download this file
126)     correctly from whoever sent it to me?" They do a good job at making
127)     sure you didn't have any random errors in your download, but they
128)     don't help you figure out whether you were downloading it from the
129)     attacker. The better question to answer is: "Is this file that I

130)     just downloaded the file that Tor intended me to get?"
131)     </p>

132)     <a class="nav" href="#TOC" title="go up">&uarr;</a>
133)   </article>
134)  </div>
135) 

136) <!-- Import Tor's signing key -->

137)  <div>
138)   <input id="ac-2" name="accordion-2" type="checkbox" checked />
139)   <label for="ac-2">

140)     <a class="nav" title="link here" href="#ImportKey">&#9668;</a>
141)     <h3><a name="ImportKey">Step 1: Import Tor's signing key</a></h3>

142)     <hr>

143)     <p>
144)     Each file on <a href="<page download/download>">our download

145)     page</a> is accompanied by a file with the same name as the
146)     package and the extension ".asc". These .asc files are GPG
147)     signatures. They allow you to verify the file you've downloaded
148)     is exactly the one that we intended you to get. For example,

149)     torbrowser-install-<version-torbrowserbundle>_en-US.exe is accompanied by
150)     torbrowser-install-<version-torbrowserbundle>_en-US.exe.asc. For a list

151)     of which developer signs which package, see our
152)     <a href="<page docs/signing-keys>">signing keys</a> page.
153)     </p>

154)   </label>

155)   <article class="ac-box">

156) 

157)    <p><span class="hint">Choose your operating system:</span>
158)    <label for="ac-2-1"><a name="KeyWindows">&#9658; Windows</a></label>

159)    <label for="ac-2-2"><a name="KeyMacOS">&#9658; macOS</a></label>

160)    <label for="ac-2-3"><a name="KeyLinux">&#9658; Linux</a></label>
161)    </p>

162) <!-- Windows -->

163)   <div>
164)    <input id="ac-2-1" name="accordion-2" type="radio" checked />
165)    <article class="ac-os">

166)     <h3>Import OpenPGP key on Windows</h3>

167)     <p>
168)     First of all you need to have GnuPG installed before you can verify
169)     signatures.
170)     <br/>
171)     Download it from
172)     <a href="https://gpg4win.org/download.html">https://gpg4win.org/download.html</a>.
173)     </p>
174)     <p>
175)     Once it's installed, use GnuPG to import the key that signed your

176)     package. In order to verify the signature you will need to type a few commands
177)     in windows command-line, <i>cmd.exe</i>.

178)     </p>
179)     <p>
180)     The Tor Browser team signs Tor Browser releases. Import its key
181)     (0x4E2C6E8793298290) by starting <i>cmd.exe</i> and typing:
182)     </p>

183)     <pre>
184)     > gpg.exe --keyserver pool.sks-keyservers.net --recv-keys 0x4E2C6E8793298290
185)     </pre>

186)     <p>

187)    </article>
188)   </div>

189) <!-- macOS -->

190)   <div>
191)    <input id="ac-2-2" name="accordion-2" type="radio" />
192)    <article class="ac-os">

193)     <h3>Import OpenPGP key on macOS</h3>

194)     <p>
195)     You need to have GnuPG installed before you can verify
196)     signatures. Install it from
197)     <a href="https://www.gpgtools.org/">https://www.gpgtools.org/</a>.
198)     </p>
199) 
200)     <p>The next step is to use GnuPG to import the key that signed
201)     your package. The Tor Browser team signs Tor Browser releases. Import its

202)     key (0x4E2C6E8793298290) by starting the terminal under
203)     "Applications/Utilities" and typing:</p>

204)     <pre>
205)     $ gpg --keyserver pool.sks-keyservers.net --recv-keys 0x4E2C6E8793298290
206)     </pre>

207)     <p>
208)    </article>
209)   </div>
210) <!-- Linux -->
211)   <div>
212)    <input id="ac-2-3" name="accordion-2" type="radio" />
213)    <article class="ac-os">

214)     <h3>Import OpenPGP key on Linux</h3>

215)     <p>
216)     You need to have GnuPG installed before you can verify

217)     signatures. It is probably already installed on your

218)     system, as most Linux distributions come with it preinstalled.
219)     </p>
220) 
221)     <p>
222)     The next step is to use GnuPG to import the key that signed
223)     your package. The Tor Browser team signs Tor Browser releases. Import its
224)     key (0x4E2C6E8793298290) by starting the terminal and typing:</p>

225)     <pre>
226)     $ gpg --keyserver pool.sks-keyservers.net --recv-keys 0x4E2C6E8793298290
227)     </pre>

228)     <p>
229)    </article>
230)   </div>

231) <!-- all OS -->

232)   <div>
233)     <p>

234)     After importing the key, you can verify that the fingerprint
235)     is correct:
236)     </p>

237)     <pre>
238)     gpg --fingerprint 0x4E2C6E8793298290
239)     </pre>

240)     <p>You should see:</p>
241)     <pre>

242) pub   rsa4096/0x4E2C6E8793298290 2014-12-15 [C] [expires: 2020-08-24]
243)       Key fingerprint = EF6E 286D DA85 EA2A 4BA7  DE68 4E2C 6E87 9329 8290

244) uid                   [ unknown] Tor Browser Developers (signing key) <torbrowser@torproject.org>

245) sub   rsa4096/0xD1483FA6C3C07136 2016-08-24 [S] [expires: 2018-08-24]
246)       Key fingerprint = A430 0A6B C93C 0877 A445  1486 D148 3FA6 C3C0 7136
247) sub   rsa4096/0xEB774491D9FF06E2 2018-05-26 [S] [expires: 2020-09-12]
248)       Key fingerprint = 1107 75B5 D101 FB36 BC6C  911B EB77 4491 D9FF 06E2

249)     </pre>

250)     <a class="nav" href="#TOC" title="go up">&uarr;</a>
251)   </div>

252)  </article><!-- END ac-box -->
253) </div><!-- END step 1 -->

254) 
255) <!-- Verifiy with OpenPGP signature -->
256) <div>
257)  <input id="ac-3" name="accordion-3" type="checkbox" />
258)  <label for="ac-3">
259)     <a class="nav" title="link here" href="#VerifySignature">&#9668;</a>

260)     <h3><a name="VerifySignature">Step 2: Verification with OpenGPG signature</a></h3>

261)     <hr>
262)     <p>This section explains how to verify the downloaded file's digital
263)     signature on different operating systems. Please notice that a signature is
264)     dated the moment the package has been signed. Therefore every time a new
265)     file is uploaded a new signature is generated with a different date. As
266)     long as you have verified the signature you should not worry that the
267)     reported date may vary.
268)     </p>
269)   </label>
270)   <article class="ac-box">
271)    <p><span class="hint">Choose your operating system:</span>
272)    <label for="ac-3-1"><a name="VerifyWindows">&#9658; Windows</a></label>

273)    <label for="ac-3-2"><a name="VerifyMacOS">&#9658; macOS</a></label>

274)    <label for="ac-3-3"><a name="VerifyLinux">&#9658; Linux</a></label>
275)    </p>
276)    <p>
277)    If you haven't already, <a href="<page download/download>">download</a>
278)    the files you are interested in.
279)    </p>
280) <!-- Windows -->
281)   <div>
282)    <input id="ac-3-1" name="accordion-3" type="radio" checked />
283)    <article class="ac-os">

284)     <h3>Verify with OpenPGP signature on Windows</h3>

285)     <p>
286)     To verify the signature of the package you downloaded, you will need

287)     to download the ".asc" file as well. Assuming you downloaded the

288)     package and its signature to your Desktop, run:
289)     </p>

290)     <pre>
291)     > gpg.exe --verify C:\Users\Alice\Desktop\torbrowser-install-<version-torbrowserbundle>_en-US.exe.asc
292)     </pre>
293) 

294)     <p>Please substitute "Alice" with your own username.</p>

295)     <p>The output should say "Good signature":</p>

296)     <pre>

297) gpg: assuming signed data in 'torbrowser-install-<version-torbrowserbundle>_en-US.exe'
298) gpg: Signature made Wed 15 Nov 2017 05:52:38 PM CET
299) gpg:                using RSA key 0xD1483FA6C3C07136

300) gpg: Good signature from "Tor Browser Developers (signing key) <torbrowser@torproject.org>" [unknown]

301) gpg: WARNING: This key is not certified with a trusted signature!
302) gpg:          There is no indication that the signature belongs to the owner.
303) Primary key fingerprint: EF6E 286D DA85 EA2A 4BA7  DE68 4E2C 6E87 9329 8290
304)      Subkey fingerprint: A430 0A6B C93C 0877 A445  1486 D148 3FA6 C3C0 7136

305)     </pre>

306)    </article>
307)   </div>

308) <!-- macOS -->

309)   <div>
310)    <input id="ac-3-2" name="accordion-3" type="radio" />
311)    <article class="ac-os">

312)     <h3>Verify with OpenPGP signature on macOS</h3>

313)     <p>

314)     To verify the signature of the package you downloaded, you will need
315)     to download the ".asc" file as well. Assuming you downloaded the
316)     package and its signature to your Downloads folder, run:

317)     </p>

318) 

319)     <p>

320)     The easiest way to verify an ".asc" file is to open it by double-clicking

321)     on it, or typing command-O. Alternatively type into the terminal:

322)     </p>
323) 

324)     <pre>
325)     $ gpg --verify ~/Downloads/TorBrowser-<version-torbrowserbundleosx64>_en-US.dmg{.asc*,}
326)     </pre>

327) 
328)     <p>The output should say "Good signature":</p>

329) 

330)     <pre>

331) gpg: assuming signed data in 'TorBrowser-<version-torbrowserbundleosx64>_en-US.dmg'

332) gpg: Signature made Wed 15 Nov 2017 05:52:38 PM CET
333) gpg:                using RSA key 0xD1483FA6C3C07136
334) gpg: Good signature from "Tor Browser Developers (signing key) <torbrowser@torproject.org>" [unknown]
335) gpg: WARNING: This key is not certified with a trusted signature!
336) gpg:          There is no indication that the signature belongs to the owner.
337) Primary key fingerprint: EF6E 286D DA85 EA2A 4BA7  DE68 4E2C 6E87 9329 8290
338)      Subkey fingerprint: A430 0A6B C93C 0877 A445  1486 D148 3FA6 C3C0 7136

339)     </pre>

340)    </article>
341)   </div>
342) <!-- Linux -->
343)   <div>
344)    <input id="ac-3-3" name="accordion-3" type="radio" />
345)    <article class="ac-os">

346)     <h3>Verify with OpenPGP signature on Linux</h3>

347) 
348)     <p>For Tor (not Tor Browser) packages:
349)     On <b>Debian</b> you should read the instructions on
350)     <a href="<page docs/debian>#packages">importing these keys to apt</a>
351)     to use our package repository instead.
352)     If you're using the <b>RPMs</b>, you can manually verify the signatures by
353)     <pre>rpm -K filename.rpm</pre>
354)     </p>
355) 

356)     <p>
357)     To verify the signature of the package you downloaded, you will need

358)     to download the ".asc" file as well. Assuming you downloaded the

359)     package and its signature to your Downloads folder, run:
360)     </p>

361) 

362)     <p>Change 64 to 32 if you have the 32-bit package:</p>

363) 

364)     <pre>
365)     $ gpg --verify tor-browser-linux64-<version-torbrowserbundlelinux64>_en-US.tar.xz.asc
366)     </pre>

367) 

368)     <p>The output should say "Good signature":</p>

369) 

370)     <pre>

371) gpg: assuming signed data in 'tor-browser-linux64-<version-torbrowserbundlelinux64>_en-US.tar.xz'
372) gpg: Signature made Wed 15 Nov 2017 05:52:38 PM CET
373) gpg:                using RSA key 0xD1483FA6C3C07136

374) gpg: Good signature from "Tor Browser Developers (signing key) <torbrowser@torproject.org>" [unknown]

375) gpg: WARNING: This key is not certified with a trusted signature!
376) gpg:          There is no indication that the signature belongs to the owner.
377) Primary key fingerprint: EF6E 286D DA85 EA2A 4BA7  DE68 4E2C 6E87 9329 8290
378)      Subkey fingerprint: A430 0A6B C93C 0877 A445  1486 D148 3FA6 C3C0 7136
379)     </pre>

380) 
381)   </article>
382)  </div>
383) <!-- END OS specific sections -->

384)     <p>
385)     Currently valid subkey fingerprints are:
386)     </p>

387)     <pre>
388)     5242 013F 02AF C851 B1C7  36B8 7017 ADCE F65C 2036

389)     BA1E E421 BBB4 5263 180E  1FC7 2E1A C68E D408 14E0

390)     A430 0A6B C93C 0877 A445  1486 D148 3FA6 C3C0 7136
391)     </pre>

392)     <p>
393)     Notice that there is a warning because you haven't assigned a trust
394)     index to this person. This means that GnuPG verified that the key made
395)     that signature, but it's up to you to decide if that key really belongs

396)     to the developer. Since international travel to meet the developer might be
397)     unfeasable you can ignore this warning or try to use another device or
398)     another internet connection to compare the key fingerprints listed

399)     <a href="<page docs/signing-keys>">here</a>.

400)     </p>

401) 

402)     <p>To learn more about GnuPG see
403)     <a href="https://www.gnupg.org/documentation/">https://www.gnupg.org/documentation/</a>

404)     </p>

405) 

406)     <a class="nav" href="#TOC" title="go up">&uarr;</a>

407)   </article><!-- END ac-box -->
408)  </div><!-- END step 2 -->

409) 

410) <!-- Verify checksums -->

411)  <div>

412)   <input id="ac-4" name="accordion-4" type="checkbox" />
413)    <label for="ac-4">
414)     <a class="nav" title="link here" href="#ChecksumVerification">&#9668;</a>

415)     <h3><a id="ChecksumVerification">Step 3: Verify the file integrity
416)     with a sha256 checksums</a></h3>

417)     <hr>

418)     <p>
419)     Build reproducibility is a
420)     <a href="https://blog.torproject.org/blog/deterministic-builds-part-one-cyberwar-and-global-compromise">
421)     security property</a> of Tor Browser 3.0 and later. Anyone can build
422)     Tor Browser on their own machine and produce a binary that is bit-for-bit
423)     identical to the binary we offer on the download page.
424)     Fortunately, it is not necessary for everyone to build Tor Browser locally
425)     to get this security. Verifying and comparing the signed list of
426)     <a href="https://en.wikipedia.org/wiki/Cryptographic_hash">hashes</a>
427)     will confirm that multiple people have built Tor Browsers identical to the
428)     download.
429)     </p>

430)    </label>

431)   <article>
432)     <p>

433)     Note: This process does not work on macOS yet due to Apple's codesigning
434)     requirement. See <a href="#MARVerification">MAR verification</a> below.

435)     </p>
436)      <ul>
437)       <li>
438)       <a href="<page download/download>">Download</a> the Tor Browser package,
439)       the <tt>sha256sums-unsigned-build.txt</tt> file, and the
440)       <tt>sha256sums-unsigned-build.txt.asc</tt> signature file.

441)       They can all be found in the same directory under
442)       <a href="https://www.torproject.org/dist/torbrowser/">

443)       https://www.torproject.org/dist/torbrowser/</a>, for example in
444)       '<version-torbrowserbundlelinux64>'

445)       for Tor Browser <version-torbrowserbundlelinux64>.

446)       </li>
447)       <li>

448)       Retrieve the signers' GPG key with following ID with the method
449)       <a href="#ImportKey">described above</a>:<br/>

450)       (Other developers' key IDs can be found
451)       <a href="<page docs/signing-keys>">here)</a>
452)       </li>

453)      </ul>

454)      <pre>
455)      0x4E2C6E8793298290
456)      </pre>

457)   </article>
458)   <article class="ac-box">
459)   
460)    <p><span class="hint">Choose your operating system:</span>
461)    <span>
462) 
463)     <label for="ac-4-1"><a name="ChecksumsWindows">&#9658; Windows</a></label>
464)    </span>
465)    <span>
466)     <label for="ac-4-3"><a name="ChecksumsLinux">&#9658; Linux</a></label>
467)    </span>
468)    </p>
469) 
470) <!-- Windows -->
471)   <div>

472)     <input id="ac-4-1" name="accordion-4" type="radio" checked />

473)    <article class="ac-os">
474)     <h3>Verififcation with a checksum on Windows</h3>
475)     <h4>Verify the signature of the checksum file</h4>
476)     <p>
477)     Verify the sha256sums-unsigned-build.txt file by executing this command:
478)     </p>

479)     <pre>
480)     > gpg.exe --verify sha256sums-unsigned-build.txt.asc sha256sums-unsigned-build.txt

481)     </pre>
482) 
483)     <p>
484)     You should see a message like
485)     <pre>"Good signature from &lt;DEVELOPER NAME&gt;"</pre>.
486)     If you don't, there is a problem. Try these steps again.
487)     </p>

488) 

489)     <h4>Verify the file integrity of Tor Browser</h4>

490)     <p>
491)     If you want to verify a Windows Tor Browser package you need to first
492)     strip off the authenticode signature of it.<br/>
493)     Tools that can be used for this purpose are
494)     <a href="http://osslsigncode.sourceforge.net">osslsigncode</a> and
495)     <a href="http://forum.xda-developers.com/showthread.php?t=416175">delcert.exe</a>.
496)     Assuming you have built e.g. <tt>osslsigncode</tt> on a Linux computer you can enter
497)     </p>
498)     <pre>
499)     > C:\path\to\osslsigncode remove-signature &#92;
500)         where\you\saved\\&lt;TOR BROWSER FILE NAME&gt;.exe &lt;TOR BROWSER FILE NAME&gt;.exe
501)     </pre>

502) 

503)     <p>Now use the sha256sum of the Tor Browser package with the
504)     <a href="http://md5deep.sourceforge.net/">hashdeep utility</a> and run
505)     </p>
506)     <pre>
507)     C:\location\of\hashdeep -c sha256sum &lt;TOR BROWSER FILE NAME&gt;.exe
508)     </pre>

509)    </article>
510)   </div>

511) 

512) <!-- Linux -->

513)   <div>
514)    <input id="ac-4-3" name="accordion-4" type="radio" />

515)    <article class="ac-os ac-4-3">
516)     <h3>Verififcation with a checksum on Linux</h3>
517)     <h4>Verify the signature of the checksum file</h4>
518)     <ul>
519)      <li>Verify the sha256sums-unsigned-build.txt with this command:</li>

520)      <pre>$ gpg --verify sha256sums-unsigned-build.txt.asc sha256sums-unsigned-build.txt</pre>

521) 

522)      <li><!-- TODO which OSs are meant here? -->

523)      In case your operating system is adding the .txt extension automatically
524)      to the SHA256 sums signature file strip it again by running

525)      </li>
526)      <pre>$ mv sha256sums-unsigned-build.txt.asc.txt sha256sums-unsigned-build.txt.asc</pre>

527) 

528)      <li>

529)      Verify the sha256sums-unsigned-build.txt file by executing this command:
530)      </li>

531)      <pre>$ gpg --verify sha256sums-unsigned-build.txt.asc sha256sums-unsigned-build.txt</pre>

532) 
533)      <li>

534)      If you don't see a message like this, there is a problem
535)      and you should try these steps again:

536)      </li>

537)      <pre>"Good signature from &lt;DEVELOPER NAME&gt;"</pre>.

538)     </ul>
539) 
540)     <h4>Verify the file integrity of Tor Browser</h4>
541)     <ul>
542)      <li>Calculate the SHA-256 checksum of Tor Browser:</li>

543)      <pre>$ sha256sum &lt;TOR BROWSER FILE NAME&gt;.tar.gz</pre>

544) 

545)      <li>You will see a string of letters and numbers.</li>

546) 

547)      <li>Open <tt>sha256sums-unsigned-build.txt</tt> in a text editor.</li>

548) 

549)      <li>Locate the name of the Tor Browser file you downloaded.</li>

550) 

551)      <li>
552)      Compare the string of letters and numbers to the left of your filename with
553)      the string of letters and numbers that appeared on your command line.
554)      If they match, you've successfully verified the build.
555)      </li>

556)     </ul>

557)     </article>
558)    </div>

559)    <a class="nav" href="#TOC" title="go up">&uarr;</a>

560)   </article><!-- END ac-box -->
561)  </div><!-- END step 3 -->

562) 
563) <!-- MAR verification -->
564)  <div>

565)   <input id="ac-5" name="accordion-5" type="checkbox" />
566)    <label for="ac-5">

567)     <a class="nav" title="link here" href="#MARVerification">&#9668;</a>

568)     <h3><a name="MARVerification">MAR verification</a></h3>

569)     <hr>

570)     <p>
571)     Starting with Tor Browser 4.5a4 we sign our MAR files which helps

572)     securing our update process. The downside of this is the need for additional
573)     instructions to verify that the MAR files we ship are indeed the ones we

574)     produced with our rbm setup.
575)     </p>
576)    </label>
577)    <article class="ac-small">
578)     <p>
579)     Assuming the verification happens on a Linux computer one first needs the

580)     <tt>mar-tools-linux*.zip</tt> out of the <tt>gitian-builder/inputs</tt>
581)     directory to remove the embedded signature(s). The steps to get the unsigned
582)     MAR file on a 64 bit Linux are</p>
583)     <pre>

584)     $ cd /path/to/MAR/file
585)     $ unzip /path/to/gitian-builder/inputs/mar-tools-linux64.zip
586)     $ export LD_LIBRARY_PATH=/path/to/MAR/file/mar-tools
587)     $ mar-tools/signmar -r your-signed-mar-file.mar your-unsigned-mar-file.mar</pre>

588)     <p>Now you can compare the SHA256 sum of <tt>your-unsigned-mar-file.mar</tt>

589)     with the one provided in the <tt>sha265sums-unsigned-build.txt</tt> or
590)     <tt>sha256sums-unsigned-build.incremental.txt</tt> as outlined in

591)     <a href="#ChekcksumVerification">Checksum verification</a> above.
592)     </p>
593)    </article>
594)  </div>
595) 
596) <!-- Troubleshooting -->
597)  <div>
598)   <input id="ac-6" name="accordion-6" type="checkbox" />
599)    <label for="ac-6">
600)     <a class="nav" title="link here" href="#Troubleshooting">&#9668;</a>
601)     <h3><a id="Troubleshooting">Troubleshooting</a></h3>
602)     <hr>
603)     <p>Does this guide work for you? Is a question missing?
604)     <a href="<page about/contact>#support">Reach out to us</a>!</p>
605)    </label>
606)    <article class="ac-small">

607)     <p>Send us your question!</p>

608)     <a class="nav" href="#TOC" title="go up">&uarr;</a>
609)   </article>
610)  </div>
611) 
612) <!-- Scripts -->
613)  <div>
614)   <input id="ac-7" name="accordion-7" type="checkbox" checked />
615)    <label for="ac-7">
616)     <a class="nav" title="link here" href="#Scripts">&#9668;</a>
617)     <h3><a id="Scripts">Automate the process with a script</a></h3>
618)     <hr>
619)     <p><a href="https://github.com/isislovecruft/scripts/blob/master/verify-gitian-builder-signatures">Scripts</a>
620)     to <a href="https://tor.stackexchange.com/questions/648/how-to-verify-tor-browser-bundle-tbb-3-x">automate</a>
621)     these steps have been written, but to use them you will need to modify
622)     them yourself with the latest Tor Browser filename.</p>

623)    </label>
624)    <article class="ac-small">

625)     <p>
626)     This needs to be explained. <a href="<page getinvolved/volunteer>">Help!</a>
627)     </p>

628)     <a class="nav" href="#TOC" title="go up">&uarr;</a>
629)   </article>
630)  </div>
631) </section>

632) 

633)   </div>
634)   <!-- END MAINCOL -->
635)   <div id = "sidecol">
636) #include "side.wmi"
637) #include "info.wmi"
638)   </div>
639)   <!-- END SIDECOL -->
640) </div>
641) <!-- END CONTENT -->