can not encrypt (but decrypt) dues to missing pub key

Matthias Apitz guru at unixarea.de
Wed Apr 1 22:10:44 CEST 2020


El día Mittwoch, April 01, 2020 a las 09:42:48 +0200, Ingo Klöcker escribió:

> > $ gpg --list-public-keys --with-colons guru at unixarea.de
> > tru::1:1585750650:0:3:1:5
> > pub:e:2048:1:7BA6AC955EAA2665:1520759851:1583831851::u:::sc:::::::
> > fpr:::::::::8BCE0232807D4CCB4F8800D17BA6AC955EAA2665:
> > uid:e::::1520759851::DD2F57BCBE052BF39F1E41416DB8DF884B56DB02::guru at unixarea
> > .de: sub:e:2048:1:2802AB9D46B97090:1520759851::::::e::::::
> > fpr:::::::::8D06C9C9460222C8A26181142802AB9D46B97090:
> > sub:e:2048:1:4FAD759204AFE5CB:1585762137::::::e::::::
> > fpr:::::::::D9BF745D512FEA9BBEF8923A4FAD759204AFE5CB:
> 
> As I assumed, the keys are expired, as can be seen by the :e: after pub/uid/
> sub.
> 
> If you do
> gpg --list-public-keys guru at unixarea.de
> you should see when the keys expired. (It's also listed above, but the unix 
> timestamp 1583831851 isn't easy to read for humans.)

Yes, the key expired some days ago:

$ gpg --list-public-keys  guru at unixarea.de
pub   rsa2048 2018-03-11 [SC] [expired: 2020-03-10]
      8BCE0232807D4CCB4F8800D17BA6AC955EAA2665
uid           [ expired] guru at unixarea.de

I don't know how this happened when I generated the keys.

I assume that there's no way to shift the expiration date?

If not, I will decrypt all files, generate new keys and crypt the files
again.

Thanks

	matthias
-- 
Matthias Apitz, ✉ guru at unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!



More information about the Gnupg-users mailing list