GPG problem with Tor RPM

Roger Dingledine arma at
Mon Mar 21 21:04:13 UTC 2005

On Mon, Mar 21, 2005 at 03:02:01PM +0000, Chris wrote:
> I couldn't verify the RPMs using GPG:
>   rpm -K tor-
>   tor- sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#28988bf5) 
> I do have the gpg key installed -- I did this:
>   rpm --import tor.asc
>   warning: tor- V3 DSA signature: NOKEY, key ID 28988bf5

My first guess is that you're failing to import my key into your rpm db.
Have you gotten this working with other programs, and other keys? Some
versions of rpm are rumored to have bugs where rpm --import silently

I just repeated these steps on my FC1 machine, and it claims to be
missing the key too. So it's not that it's getting a *bad* signature,
it just fails to learn about the key.

rpm -K works fine for me on my RC73 machine (where rpm actually uses gpg).

In any case, I double-checked and the rpms available from
are still in fact the ones that I uploaded, so I think all is well on
that front.

This is why I've been pushing Jeff Moe (cc'ed) to handle our RPM
distribution. I'm just winging it, and tend to put actual Tor development
higher priority. :)

>   cd `rpm --eval '%{_sourcedir}'`
>   wget
>   gpg --verify tor- 
>   gpg: Signature made Wed 23 Feb 2005 06:33:29 GMT using DSA key ID 28988BF5
>   gpg: BAD signature from "Roger Dingledine <arma at>"

Right, this is because our "make dist-rpm" builds its own tarball and
then makes an rpm out of it. So it won't use the same tarball as is
uploaded to the site. If anybody wants to submit a patch to make it use
the official tarball, that would be great.

> However I then got the tgz from the site, checked the sig
> OK and built my own RPM using that and it was OK.



More information about the tor-dev mailing list