en/verifying-signatures.wml (8a47cf351) - tor-webwml.git

verifying-signatures.wml

## translation metadata
# Revision: $Revision$
# Translation-Priority: 2-medium

#include "head.wmi" TITLE="Verifying Signatures" CHARSET="UTF-8"

<h2>Verifying signatures on released files</h2>
<hr />

Each file on <a href="<page download>">our download page</a> is accompanied
by a file with the same name and the extension ".asc".

These are PGP signatures, so you can verify that the file you've downloaded
is exactly the one that we intended you to get.

Of course, you'll need to have our pgp keys in your keyring: if you don't
know the pgp key, you can't be sure that it was really us who signed it. The
signing keys we use are Roger's (0x28988BF5) and Nick's (0x165733EA, or its
subkey 0x8D29319A). Some binary packages may also be signed by Andrew's
(0x31B0974B), Peter's (0x94C09C7F, or its subkey 0xAFA44BDD), Matt's
(0x5FA14861), or Jacob's (0x9D0FACE4).

You can import keys directly from GnuPG as well:

<pre>gpg --keyserver subkeys.pgp.net --recv-keys 0x28988BF5</pre>

or search for keys with

<pre>gpg --keyserver subkeys.pgp.net --search-keys
0x28988BF5</pre>

and when you select one, it will be added to your keyring.

The fingerprints for the keys should be:

<pre>
pub 1024D/28988BF5 2000-02-27
 Key fingerprint = B117 2656 DFF9 83C3 042B C699 EB5A 896A 2898 8BF5
uid Roger Dingledine &lt;arma@mit.edu&gt;

pub   3072R/165733EA 2004-07-03
      Key fingerprint = B35B F85B F194 89D0 4E28  C33C 2119 4EBB 1657 33EA
uid                  Nick Mathewson &lt;nickm@alum.mit.edu&gt;
uid                  Nick Mathewson &lt;nickm@wangafu.net&gt;
uid                  Nick Mathewson &lt;nickm@freehaven.net&gt;

pub  1024D/31B0974B 2003-07-17
     Key fingerprint = 0295 9AA7 190A B9E9 027E  0736 3B9D 093F 31B0 974B
uid                  Andrew Lewman (phobos) &lt;phobos@rootme.org&gt;

pub   1024D/94C09C7F 1999-11-10
      Key fingerprint = 5B00 C96D 5D54 AEE1 206B  AF84 DE7A AF6E 94C0 9C7F
uid                  Peter Palfrader
uid                  Peter Palfrader &lt;peter@palfrader.org&gt;
uid                  Peter Palfrader &lt;weasel@debian.org&gt;

pub   1024D/5FA14861 2005-08-17
      Key fingerprint = 9467 294A 9985 3C9C 65CB  141D AF7E 0E43 5FA1 4861
uid                  Matt Edman &lt;edmanm@rpi.edu&gt;
uid                  Matt Edman &lt;Matt_Edman@baylor.edu&gt;
uid                  Matt Edman &lt;edmanm2@cs.rpi.edu&gt;
sub   4096g/EA654E59 2005-08-17

pub 1024D/9D0FACE4 2008-03-11 [expires: 2010-03-11]
 Key fingerprint = 12E4 04FF D3C9 31F9 3405 2D06 B884 1A91 9D0F ACE4
uid Jacob Appelbaum <jacob@appelbaum.net>
sub 4096g/D5E87583 2008-03-11 [expires: 2010-03-11]
</pre>

(Of course if you want to be really certain that those are the real ones
then you should check this from more places or even better get into key signing
and build a trust path to those keys.)

If you're using GnuPG, then put the .asc and the download in the same
directory and type "gpg --verify (whatever).asc (whatever)". It will say
something like "Good signature" or "BAD signature" using the following type of
command:

<pre>
gpg --verify tor-0.1.0.17.tar.gz.asc tor-0.1.0.17.tar.gz
gpg: Signature made Wed Feb 23 01:33:29 2005 EST using DSA key ID 28988BF5
gpg: Good signature from "Roger Dingledine &lt;arma@mit.edu&gt;"
gpg: aka "Roger Dingledine &lt;arma@mit.edu&gt;"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: B117 2656 DFF9 83C3 042B C699 EB5A 896A 2898 8BF5
</pre>

Notice that there is a warning because you haven't assigned a trust index to
this user. This means that your program verified the key made that signature.
It's up to the user to decide if that key really belongs to the developers. The
best method is to meet them in person and exchange gpg fingerprints. Keys can
also be signed. If you look up Roger or Nick's keys, other people have
essentially said "we have verified this is Roger/Nick". So if you trust that
third party, then you have a level of trust for that arma/nick.

All this means is you can ignore the message or assign a trust level.

For your reference, this is an example of a BAD verification. It
means that the signature and file contents do not match:

<pre>
gpg --verify tor-0.1.0.17.tar.gz.asc
gpg: Signature made Wed Feb 23 01:33:29 2005 EST using DSA key ID 28988BF5
gpg: BAD signature from "Roger Dingledine &lt;arma@mit.edu&gt;"
</pre>

If you see a message like the above one, then you should not have any trust
in the file contents.

If you are running Tor on Debian you should read the instructions on
<a
href="https://wiki.torproject.org/noreply/TheOnionRouter/TorOnDebian">importing
these keys to apt</a>.

</div>

#include <foot.wmi>

tor-webwml.git

Add my gpg key info to the website.