Georg Koppen commited on 2016-01-12 12:59:58
Zeige 1 geänderte Dateien mit 18 Einfügungen und 21 Löschungen.
This update fixes bug 17851 by changing all http:// links to gpg related websites to https:// ones. Furthermore, it incorporates feedback Josef provided to us with respect to signature and SHA256 sums verification on OS X. Thirdly, we need to set LD_LIBRARY_PATH to be able to strip MAR signatures. And, finally, this patch cleans up the GPG output of the Tor Browser developers signing key.
... | ... |
@@ -36,7 +36,7 @@ |
36 | 36 |
you're talking to the Tor website with https when you're not.</p> |
37 | 37 |
|
38 | 38 |
<p>Some software sites list <a |
39 |
- href="http://en.wikipedia.org/wiki/Cryptographic_hash_function">sha1 |
|
39 |
+ href="https://en.wikipedia.org/wiki/Cryptographic_hash_function">sha1 |
|
40 | 40 |
hashes</a> alongside the software on their website, so users can |
41 | 41 |
verify that they downloaded the file without any errors. These |
42 | 42 |
"checksums" help you answer the question "Did I download this file |
... | ... |
@@ -60,7 +60,7 @@ |
60 | 60 |
<hr> |
61 | 61 |
<p>You need to have GnuPG installed before |
62 | 62 |
you can verify signatures. Download it from <a |
63 |
- href="http://gpg4win.org/download.html">http://gpg4win.org/download.html</a>.</p> |
|
63 |
+ href="https://gpg4win.org/download.html">https://gpg4win.org/download.html</a>.</p> |
|
64 | 64 |
<p>Once it's installed, use GnuPG to import the key that signed your |
65 | 65 |
package. Since GnuPG for Windows is a command-line tool, you will need |
66 | 66 |
to use <i>cmd.exe</i>. Unless you edit your PATH environment variable, |
... | ... |
@@ -80,7 +80,6 @@ |
80 | 80 |
uid Tor Browser Developers (signing key) <torbrowser@torproject.org> |
81 | 81 |
sub 4096R/F65C2036 2014-12-15 |
82 | 82 |
sub 4096R/D40814E0 2014-12-15 |
83 |
- sub 4096R/589839A3 2014-12-15 |
|
84 | 83 |
</pre> |
85 | 84 |
<p>To verify the signature of the package you downloaded, you will need |
86 | 85 |
to download the ".asc" file as well. Assuming you downloaded the |
... | ... |
@@ -96,8 +95,7 @@ |
96 | 95 |
<p>Currently valid subkey fingerprints are: |
97 | 96 |
<pre> |
98 | 97 |
5242 013F 02AF C851 B1C7 36B8 7017 ADCE F65C 2036 |
99 |
- BA1E E421 BBB4 5263 180E 1FC7 2E1A C68E D408 14E0 |
|
100 |
- 05FA 4425 3F6C 19A8 B7F5 18D4 2D00 0988 5898 39A3</pre></p> |
|
98 |
+ BA1E E421 BBB4 5263 180E 1FC7 2E1A C68E D408 14E0</pre></p> |
|
101 | 99 |
<p> |
102 | 100 |
Notice that there is a warning because you haven't assigned a trust |
103 | 101 |
index to this person. This means that GnuPG verified that the key made |
... | ... |
@@ -110,7 +108,7 @@ |
110 | 108 |
|
111 | 109 |
<p>You need to have GnuPG installed before you can verify |
112 | 110 |
signatures. If you are using Mac OS X, you can install it from <a |
113 |
- href="http://www.gpgtools.org/">http://www.gpgtools.org/</a>. If you |
|
111 |
+ href="https://www.gpgtools.org/">https://www.gpgtools.org/</a>. If you |
|
114 | 112 |
are using Linux, then it's probably you already have GnuPG in your |
115 | 113 |
system, as most Linux distributions come with it preinstalled. |
116 | 114 |
</p> |
... | ... |
@@ -133,16 +131,13 @@ |
133 | 131 |
Key fingerprint = EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290 |
134 | 132 |
uid Tor Browser Developers (signing key) <torbrowser@torproject.org> |
135 | 133 |
sub 4096R/F65C2036 2014-12-15 |
136 |
- sub 4096R/D40814E0 2014-12-15 |
|
137 |
- sub 4096R/589839A3 2014-12-15 |
|
138 |
- </pre> |
|
139 |
- |
|
134 |
+ sub 4096R/D40814E0 2014-12-15</pre> |
|
140 | 135 |
<p>To verify the signature of the package you downloaded, you will need |
141 | 136 |
to download the ".asc" file as well. Assuming you downloaded the |
142 |
- package and its signature to your Desktop, run:</p> |
|
137 |
+ package and its signature to your Downloads folder, run:</p> |
|
143 | 138 |
|
144 | 139 |
<strong>For Mac OS X users</strong>:<br /> |
145 |
- <pre>gpg --verify ~/Desktop/TorBrowser-<version-torbrowserbundleosx64>-osx64_en-US.dmg{.asc*,}</pre> |
|
140 |
+ <pre>gpg --verify ~/Downloads/TorBrowser-<version-torbrowserbundleosx64>-osx64_en-US.dmg{.asc*,}</pre> |
|
146 | 141 |
|
147 | 142 |
<strong>For Linux users</strong> (change 32 to 64 if you have the 64-bit package):<br /> |
148 | 143 |
<pre>gpg --verify ~/Desktop/tor-browser-linux32-<version-torbrowserbundlelinux32>_en-US.tar.xz{.asc*,}</pre> |
... | ... |
@@ -157,8 +152,7 @@ |
157 | 152 |
Primary key fingerprint: EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290</pre> <p> Currently valid subkey fingerprints are: |
158 | 153 |
<pre> |
159 | 154 |
5242 013F 02AF C851 B1C7 36B8 7017 ADCE F65C 2036 |
160 |
- BA1E E421 BBB4 5263 180E 1FC7 2E1A C68E D408 14E0 |
|
161 |
- 05FA 4425 3F6C 19A8 B7F5 18D4 2D00 0988 5898 39A3</pre></p> |
|
155 |
+ BA1E E421 BBB4 5263 180E 1FC7 2E1A C68E D408 14E0</pre></p> |
|
162 | 156 |
<p> |
163 | 157 |
Notice that there is a warning because you haven't assigned a trust |
164 | 158 |
index to this person. This means that GnuPG verified that the key made |
... | ... |
@@ -177,7 +171,7 @@ |
177 | 171 |
</p> |
178 | 172 |
|
179 | 173 |
<p>See <a |
180 |
- href="http://www.gnupg.org/documentation/">http://www.gnupg.org/documentation/</a> |
|
174 |
+ href="https://www.gnupg.org/documentation/">https://www.gnupg.org/documentation/</a> |
|
181 | 175 |
to learn more about GnuPG.</p> |
182 | 176 |
|
183 | 177 |
<hr> |
... | ... |
@@ -204,14 +198,16 @@ |
204 | 198 |
file, and the <tt>sha256sums-unsigned-build.txt.asc</tt> signature file. |
205 | 199 |
They can all be found in the same directory under |
206 | 200 |
<a href="https://www.torproject.org/dist/torbrowser/"> |
207 |
- https://www.torproject.org/dist/torbrowser/</a>, for example in '4.5.1' |
|
208 |
- for Tor Browser 4.5.1.</li> |
|
201 |
+ https://www.torproject.org/dist/torbrowser/</a>, for example in '<version-torbrowserbundlelinux32>' |
|
202 |
+ for Tor Browser <version-torbrowserbundlelinux32>.</li> |
|
203 |
+ <li>In case your operating system is adding the .txt extension |
|
204 |
+ automatically to the SHA256 sums signature file strip it again by running |
|
205 |
+ <pre>mv sha256sums-unsigned-build.txt.asc.txt sha256sums-unsigned-build.txt.asc</pre> |
|
209 | 206 |
<li>Retrieve the signers' GPG keys. This can be done from the command |
210 | 207 |
line by entering something like |
211 | 208 |
<pre>gpg --keyserver keys.mozilla.org --recv-keys 0x4E2C6E8793298290</pre> |
212 | 209 |
(This will bring you the public part of the Tor Browser developers' |
213 |
- signing key. Other |
|
214 |
- developers' key IDs can be found on |
|
210 |
+ signing key. Other developers' key IDs can be found on |
|
215 | 211 |
<a href="<page docs/signing-keys>">this |
216 | 212 |
page</a>.)</li> |
217 | 213 |
<li>Verify the sha256sums-unsigned-build.txt file by executing this |
... | ... |
@@ -230,7 +226,7 @@ |
230 | 226 |
Windows you can use the <a href="http://md5deep.sourceforge.net/"> |
231 | 227 |
hashdeep utility</a> and run |
232 | 228 |
<pre>C:\location\where\you\saved\hashdeep -c sha256sum <TOR BROWSER FILE NAME>.exe</pre> |
233 |
- On Mac or Linux you can run <pre>sha256sum <TOR BROWSER FILE NAME>.dmg</pre> or <pre>sha256sum <TOR BROWSER FILE NAME>.tar.gz</pre> without having to download a utility.</li> |
|
229 |
+ On Mac or Linux you can run <pre>shasum -a 256 <TOR BROWSER FILE NAME>.dmg</pre> or <pre>sha256sum <TOR BROWSER FILE NAME>.tar.gz</pre> without having to download a utility.</li> |
|
234 | 230 |
<li>You will see a string of letters and numbers.</li> |
235 | 231 |
<li>Open <tt>sha256sums-unsigned-build.txt</tt> in a text editor.</li> |
236 | 232 |
<li>Locate the name of the Tor Browser file you downloaded.</li> |
... | ... |
@@ -241,7 +237,7 @@ |
241 | 237 |
</ul> |
242 | 238 |
|
243 | 239 |
<p><a href="https://github.com/isislovecruft/scripts/blob/master/verify-gitian-builder-signatures">Scripts</a> |
244 |
- to <a href="http://tor.stackexchange.com/questions/648/how-to-verify-tor-browser-bundle-tbb-3-x">automate</a> |
|
240 |
+ to <a href="https://tor.stackexchange.com/questions/648/how-to-verify-tor-browser-bundle-tbb-3-x">automate</a> |
|
245 | 241 |
these steps have been written, but to use them you will need to modify |
246 | 242 |
them yourself with the latest Tor Browser filename.</p> |
247 | 243 |
|
... | ... |
@@ -263,6 +259,7 @@ |
263 | 259 |
<pre> |
264 | 260 |
cd /path/to/MAR/file |
265 | 261 |
unzip /path/to/gitian-builder/inputs/mar-tools-linux64.zip |
262 |
+ export LD_LIBRARY_PATH=/path/to/MAR/file/mar-tools |
|
266 | 263 |
mar-tools/signmar -r your-signed-mar-file.mar your-unsigned-mar-file.mar</pre> |
267 | 264 |
<p>Now you can compare the SHA256 sum of <tt>your-unsigned-mar-file.mar</tt> |
268 | 265 |
with the one provided in the <tt>sha265sums-unsigned-build.txt</tt> or |
269 | 266 |