Thu Sep 20 02:43:02 2001
Content-Type: text/plain; charset=us-ascii
On Thu, Sep 20, 2001 at 01:00:11AM +0100, Nick Lamb wrote:
> Once again I tried to actually use GnuPG for something, and was pretty
> much immediately stopped short by a problem.
> Here you can see that I have created a new subkey for 1024D/741BE7D8
> and of course I have the public and private components on this local
> [njl98r@chef njl98r]$ gpg --list-keys njl98r
> pub 1024D/741BE7D8 1999-10-11 Nicholas Lamb <email@example.com>
> uid Nicholas Lamb <firstname.lastname@example.org>
> sub 1024g/427333F4 1999-10-11 [expires: 2000-11-09]
> sub 1024g/8458535B 2001-07-26 [expires: 2002-07-26]
> It would be nice if other users could have this new subkey, so that when
> they send me mail it doesn't complain about the old, expired subkey
> [njl98r@chef njl98r]$ gpg --send-keys 741BE7D8
> gpg: success sending to `wwwkeys.pgp.net' (status=3D200)
> However it appears that either GnuPG never bothers to tell the server
> about the new subkey, or the server never bothers to record it. When
> I look at the key list on other people's systems (yes, from the same
> server after I updated it) the new subkey is missing.
> What am I doing wrong? How do I make it do what I (obviously) intended?
You're doing it just right, and so is GnuPG. There is, alas, a bug in
some of the HKP keyservers that makes them unable to handle keys with
I'm afraid I don't know exactly *which* keyservers are buggy.
certserver.pgp.com is known good, but is not a HKP keyserver so you
need to use the web interface or my LDAP keyserver addition to GnuPG.
I believe pgp.dtype.org is good as well, and it's a HKP server.
David Shaw | email@example.com | WWW http://www.jabberwocky.com/
"There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence." - Jeremy S. Anderson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----