Hi,
I am new to this forum and hope to helpt o fix a error (or to teach me that I am wrong)
I have a key which I extended till 2014-03-06 - on my linux gpg this is displayed right:
Linux:
gpg --recv-keys 0x88fc422e096ee8bd
gpg --list-keys
/home/pi/.gnupg/pubring.gpg
---------------------------
pub 2048R/096EE8BD 2012-03-27 [expires: 2014-03-26]
uid Eugen Frank Albiker (Neue Emailadresse 07/2012) <eugen@eugenalbiker.de>
uid Eugen Frank Albiker <EugenAlbiker@onlinehome.de>
As you can see the key expires at 2014-03-26
But when I have installes gpg4win (V2.2.0) on my windows maschine, i had this output:
Windows:
pub 2048R/096EE8BD erzeugt: 2012-03-27 verfallen: 2013-03-26 Aufruf: SCE
Vertrauen: unbekannt G³ltigkeit: verfallen
[verfall.] (1). Eugen Frank Albiker (Neue Emailadresse 07/2012) <eugen@eugenalbi
ker.de>
[verfall.] (2) Eugen Frank Albiker <EugenAlbiker@onlinehome.de>
you see that my kay had already expired at 2013-03-26
What do I wrong? or ist this a erroro in gpg??
Greetings
eugen
Not sure what caused the problem. Can you try changing the expiration date? In Kleopatra, right-click the key and select “Change Expiry Date…”
Alternatively, in the command prompt:
C:>gpg --edit-key 08321C8F
gpg (GnuPG) 2.0.21; Copyright (C) 2013 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Secret key is available.
pub 2048R/08321C8F created: 2013-08-26 expires: 2016-08-25 usage: SC
trust: ultimate validity: ultimate
sub 2048R/FF327F86 created: 2013-08-26 expires: 2016-08-25 usage: E
[ultimate] (1). Test Cert (For Testing Only) sample@mail.com
gpg> expire
Changing expiration time for the primary key.
Please specify how long the key should be valid.
0 = key does not expire
= key expires in n days
w = key expires in n weeks
m = key expires in n months
y = key expires in n years
Key is valid for? (0) 1y
Key expires at 08/26/14 00:47:10 Eastern Daylight Time
Is this correct? (y/N) y
You need a passphrase to unlock the secret key for
user: “Test Cert (For Testing Only) sample@mail.com”
2048-bit RSA key, ID 08321C8F, created 2013-08-26
pub 2048R/08321C8F created: 2013-08-26 expires: 2014-08-26 usage: SC
trust: ultimate validity: ultimate
sub 2048R/FF327F86 created: 2013-08-26 expires: 2016-08-25 usage: E
[ultimate] (1). Test Cert (For Testing Only) sample@mail.com
gpg> quit
Save changes? (y/N) y
C:>
Hi,
thanks for the response.
ok, I have now changed the expire date to 2014-08-27 and saved it. i have done this on my linux system, because i have here my private key…
see:
pub 2048R/096EE8BD erzeugt: 2012-03-27 verfällt: 2014-08-27 Aufruf: SCE
Vertrauen: uneingeschränkt Gültigkeit: uneingeschränkt
[uneingeschränkt] (1). Eugen Frank Albiker (Neue Emailadresse 07/2012) eugen@eugenalbiker.de
[uneingeschränkt] (2) Eugen Frank Albiker EugenAlbiker@onlinehome.de
Then I went to my windows 7 system (with gpg4win 2.2.0, Outlook 2007, Kleopatra 2.2.0) and deleted my key and after that I get the key newly from the keyserver.
Kleopatra show now the expire date “2013-03-26” - but this was my old expire date!
The new and the actual expire date is “2014-08-27”
I did a new install of gpg4win in a other virtual machine - and all is right! the correct expire date!
Then I went to the machine with the wrong expire date, and deleted my key in kleopatra and get it new from the server. Now also here is all ok!!
What the problem was, I couln’t find out… Perhaps the change of the expire date was the cause, that all is right now…
if I could help to find the real error, don’t hesitate to ask me - I’m lucky to help.
Greetings
The keyservers only supply a public key, and the key you uploaded may not have propagated to that server. I’ve noticed that sometimes, depending on the server, it takes a little bit to make your newly uploaded keys available. It would probably be quicker to simply load your updated keys locally.