My gpg encryption subkey expired recently; I created a new subkey; it's
signed, expires in a few months, etc. The key imports fine when I pull
it in from the ascii armored export version ... but exporting it to the
keyserver via --send-key fails miserably. I get a report of success,
but when I --recv-key, I don't get the new subkey.
(below: my public/private keypair resides on "meteu". "fury" is another
host, which does not have either key.)
----
meteu:~ 2% gpg --send-key flip
gpg: success sending to `wwwkeys.us.pgp.net' (status=200)
meteu:~ 3% gpg --export -a flip > /var/www/public.asc
meteu:~ 4% gpg --list-key flip
pub 1024D/17984F07 2001-10-06 Chris Flipse <flip@csh.rit.edu>
uid Chris Flipse <flip@octoraro.org>
uid Chris Flipse <flip@athas.org>
sub 1024g/B03178DE 2001-10-06 [expires: 2002-04-04]
sub 1024g/BCA91458 2002-05-09 [expires: 2002-11-05]
pub 1024D/17984F07 2001-10-06 Chris Flipse <flip@csh.rit.edu>
uid Chris Flipse <flip@octoraro.org>
uid Chris Flipse <flip@athas.org>
sub 1024g/B03178DE 2001-10-06 [expires: 2002-04-04]
sub 1024g/BCA91458 2002-05-09 [expires: 2002-11-05]
meteu:~ 5%
----
New subkey exists, supposedly got exported to wwwkeys.us.pgp.net
alright. However.
----
fury:~ 40% gpg --list-key flip
gpg: Warning: using insecure memory!
gpg: error reading key: public key not found
fury:~ 41% wget http://meteu.octoraro.org/public.asc
--11:46:10-- http://meteu.octoraro.org/public.asc
=> `public.asc'
Connecting to meteu.octoraro.org:80... connected!
HTTP request sent, awaiting response... 200 OK
Length: 2,265 [text/plain]
0K .. 100% @ 44.24 KB/s
11:46:10 (44.24 KB/s) - `public.asc' saved [2265/2265]
fury:~ 42% gpg --import public.asc
gpg: Warning: using insecure memory!
gpg: key 17984F07: public key imported
gpg: Total number processed: 1
gpg: imported: 1
fury:~ 43% gpg --list-key flip
gpg: Warning: using insecure memory!
pub 1024D/17984F07 2001-10-06 Chris Flipse <flip@csh.rit.edu>
uid Chris Flipse <flip@octoraro.org>
uid Chris Flipse <flip@athas.org>
sub 1024g/B03178DE 2001-10-06 [expires: 2002-04-04]
sub 1024g/BCA91458 2002-05-09 [expires: 2002-11-05]
fury:~ 44%
----
Key is imported just fine from the ascii armored export. No problems.
----
fury:~ 44% gpg --delete-key flip
gpg: Warning: using insecure memory!
pub 1024D/17984F07 2001-10-06 Chris Flipse <flip@csh.rit.edu>
Delete this key from the keyring? yes
fury:~ 45% gpg --list-key flip
gpg: Warning: using insecure memory!
gpg: error reading key: public key not found
fury:~ 46% gpg --recv-key 17984F07
gpg: Warning: using insecure memory!
gpg: requesting key 17984F07 from wwwkeys.us.pgp.net ...
gpg: key 17984F07: public key imported
gpg: Total number processed: 1
gpg: imported: 1
fury:~ 47% gpg --list-key flip
gpg: Warning: using insecure memory!
pub 1024D/17984F07 2001-10-06 Chris Flipse <flip@csh.rit.edu>
uid Chris Flipse <flip@octoraro.org>
uid Chris Flipse <flip@athas.org>
sub 1024g/B03178DE 2001-10-06 [expires: 2002-04-04]
fury:~ 48%
----
Apparently, the version of the key up on the PGP server doesn't have the
new subkey. So, what am I missing?
--
// [pgp] 1024D/17984F07 [http] meteu.octoraro.org
Nice, selfless people don't restore my faith in humanity -- they restore
my faith in randomness.
Attachment:
pgpih5jOvKCSe.pgp
Description: PGP signature