Combined osx and linux instructions
ilv

ilv commited on 2015-02-11 20:56:33
Zeige 1 geänderte Dateien mit 23 Einfügungen und 26 Löschungen.

... ...
@@ -103,18 +103,20 @@
103 103
     to the developer. The best method is to meet the developer in person and
104 104
     exchange key fingerprints.
105 105
     </p>
106
-    <h3>Mac OS X</h3>
106
+    <h3>Mac OS X and Linux</h3>
107 107
     <hr>
108 108
 
109 109
     <p>You need to have GnuPG installed before you can verify
110
-    signatures. You can install it from <a
111
-    href="http://www.gpgtools.org/">http://www.gpgtools.org/</a>.
110
+    signatures. If you are using Mac OS X, you can install it from <a
111
+    href="http://www.gpgtools.org/">http://www.gpgtools.org/</a>. If you
112
+    are using Linux, then it's probably you already have GnuPG in your
113
+    system, as most Linux distributions come with it preinstalled.
112 114
     </p>
113 115
 
114
-    <p>Once it's installed, use GnuPG to import the key that signed
116
+    <p>The next step is to use GnuPG to import the key that signed
115 117
     your package. Erinn Clark signs the Tor Browsers. Import her
116
-    key (0x416F061063FEE659) by starting the terminal (under "Applications")
117
-    and typing:</p>
118
+    key (0x416F061063FEE659) by starting the terminal (under "Applications"
119
+    in Mac OS X) and typing:</p>
118 120
 
119 121
     <pre>gpg --keyserver x-hkp://pool.sks-keyservers.net --recv-keys 0x416F061063FEE659</pre>
120 122
 
... ...
@@ -135,9 +137,14 @@
135 137
 
136 138
     <p>To verify the signature of the package you downloaded, you will need
137 139
     to download the ".asc" file as well. Assuming you downloaded the
138
-    package and its signature to your Desktop, run:</p>
140
+    package and its signature to your Desktop, run (where <version> stands
141
+    for the version of Tor Browser you downloaded):</p>
142
+
143
+    <strong>For Mac OS X users</strong>:
144
+    <pre>gpg --verify ~/Desktop/TorBrowser-<version>-osx32_en-US.dmg{.asc*,}</pre>
139 145
     
140
-    <pre>gpg --verify ~/Desktop/TorBrowser-<version-torbrowserbundleosx32>-osx32_en-US.dmg{.asc*,}</pre>
146
+    <strong>For Linux users</strong> (change 32 by 64 if you have the 64-bit package):
147
+    <pre>gpg --verify ~/Desktop/tor-browser-linux32-<version>_en-US.tar.xz{.asc*,}</pre>
141 148
 
142 149
     <p>The output should say "Good signature": </p>
143 150
 
... ...
@@ -159,29 +166,19 @@
159 166
     exchange key fingerprints.
160 167
     </p>
161 168
     
162
-    <h3>Linux</h3>
163
-    <hr>
164
-
165
-    <p>Most Linux distributions come with gpg preinstalled, so users
166
-    who want to verify the Tor Browser for Linux (or the source
167
-    tarball) can just follow along with the instructions above for
168
-    "Mac OS X". </p>
169
-
170
-    <p>If you're using the <b>Debian</b> Tor (not Tor Browser) packages, you 
171
-    should read the
172
-    instructions on <a href="<page docs/debian>#packages">importing
173
-    these keys to apt</a>.</p>
174
-
175
-    <p>If you're using the <b>RPMs</b> (for Tor, not Tor Browser), you can 
176
-    manually verify the
177
-    signatures on the RPM packages by <pre>rpm -K filename.rpm</pre></p>
169
+    <p>
170
+    If you're a Linux user and you're using the <b>Debian</b> Tor (not Tor
171
+    Browser) packages, you should read the instructions on <a
172
+    href="<page docs/debian>#packages">importing these keys to apt</a>.
173
+    If you're using the <b>RPMs</b> (for Tor, not Tor Browser), you can
174
+    manually verify the signatures on the RPM packages by
175
+    <pre>rpm -K filename.rpm</pre>
176
+    </p>
178 177
 
179 178
     <p>See <a
180 179
     href="http://www.gnupg.org/documentation/">http://www.gnupg.org/documentation/</a>
181 180
     to learn more about GPG.</p>
182 181
 
183
-    <hr>
184
-
185 182
     <a id="BuildVerification"></a>
186 183
     <h3><a class="anchor" href="#BuildVerification">
187 184
     Verifying sha256sums (advanced)</a></h3>
188 185