RSA sign key id being modified on MIT PGP keyserver

David Shaw dshaw@jabberwocky.com
Tue Mar 11 15:21:02 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Mar 11, 2003 at 04:49:32AM +0100, Andy McDowell wrote:

> I have subscribed here to find an answer to a pain-in-the-arse problem
> to do with my 4096b RSA sign-only public key ID being modified when the
> key is uploaded to the MIT PGP keyserver.
> 
> I see this problem has already been discussed in the thread "Problem
> with GnuPG 1.2.1 generated Key (Broken Key or Keyserver Problem)" -
> OP'er Bjoern Buerger.
> 
> David Shaw wrote back and said he had a patch prepared and it was
> waiting for release.

It was released a few weeks ago as part of pks 0.9.6.

> So just a couple of questions to follow up.
> 
> - -1- After the patch is applied will the RSA (public) key need to be
> uploaded once again to the MIT PGP keyserver to correct the key id, or
> will the key id be corrected automatically once the key applied?

Automatically corrected.

> - -2- Is there any timeline for when the patch will be applied to the
> keyserver?

You'll have to ask the pgp.mit.edu administrator.  I do know they were
testing the new keyserver version, but I don't know what their plans
are.  The pks software is changing fast, so they may be waiting for
the next release.

> - -3- Is there a preferred alternative keyserver for GPG generated keys,
> where the key id's for RSA keys are not modified?

There are a few keyservers that have upgraded, or who don't run pks so
the bug never applied to them.  Try:

   keyserver.bu.edu
   blackhole.pca.dfn.de
   pgp.cns.ualberta.ca
   keyserver.stinkfoot.org
   keyserver.kjsl.com

You can also use the PGP.com LDAP server: ldap://keys.pgp.com

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2rc1 (GNU/Linux)
Comment: http://www.jabberwocky.com/david/keys.asc

iD8DBQE+bfDc4mZch0nhy8kRAq8mAKCJQJjfNU+EX11bojnLKHwAtGkAuACgmIkV
AZxlbXYCVxRlnxLQ2Pxx+2k=
=zX4v
-----END PGP SIGNATURE-----