Joseph wrote:
> I'm using gnupg-1.9.21
Huh. That's an old version of gnupg2. It may well have the same bug
in it that the gnupg 1.x branch had. Try updating your gpg package.
> and I tried it both with "0x" and without.
>
> gpg --interactive --recv-keys ED0E1FB7
> worked but it gives me an old unmodified version.
>
> I tried to submit
> gpg --send-keys 0xED0E1FB7
> gpg --send-keys ED0E1FB7
>
> both went though fine (I think) no complains.
> Except I think it doesn't work.
> I have removed/updated most keyid's and change expiration to
> unlimited. but it pulls back expired version.
> pub 1024D/ED0E1FB7 created: 2002-05-09 expires: 2005-02-02
You may have something still on your keyring or on your key which has
the expiration date. That can cause gpg to still show the key as
expired. It's worth noting that you cannot remove anything from the
keyservers. If you have user id's or other parts of your key that you
don't like, you can revoke them, but you can't simply delete them from
your local copy and then re-upload the key. This is something that
often bites new (and sometimes old) gpg users.
You may want to do some googling and then ask on the gnupg-users list
for more specific gpg help.
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A statesman is a dead politician. Lord knows, we need more statesmen.
-- Opus
Attachment:
pgpnkI5lnh4Ji.pgp
Description: PGP signature