LinuxQuestions.org - [SOLVED] GPG Key Problem

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - GPG Key Problem (https://www.linuxquestions.org/questions/slackware-14/gpg-key-problem-4175676150/)

I am using gpg4win on windows 10 to verify my slackware ISO for another computer. The key fingerprint matches perfectly and so does everything else, but it reports as [e] for expired and has expires ????-??-?? has the expiration date. I believe that this is because of dates past 2038, but I'm not entirely sure. So is this a problem with the public slackware key or is this a problem with gpg4win? Has anyone else had this issue?

Have you verified the date on your system is correct and set to the correct timezone? Usually when I get errors with certificates, it's because the system time is off.

Quote:

Originally Posted by bassmadrigal (Post 6128784)

Have you verified the date on your system is correct and set to the correct timezone? Usually when I get errors with certificates, it's because the system time is off.

I can confirm that my timezone is set to the correct one and that my clock matches the correct time.

@ziprun

I can confirm this in command prompt under Win7 (have no Win10 ATM) with the latest gpg4win.
Got the key from http://www.slackware.com/gpg-key and imported it:

Code:

E:\>gpg --import gpg-key

gpg: key 6A4463C040102233: public key "Slackware Linux Project <security@slackware.com>" imported

gpg: Total number processed: 1

gpg:              imported: 1

E:\>gpg --list-keys 6A4463C040102233

pub  dsa1024 2003-02-26 [SCA] [expires: ????-??-??]

      EC5649DA401E22ABFA6736EF6A4463C040102233

uid          [ unknown] Slackware Linux Project <security@slackware.com>

sub  elg1024 2003-02-26 [E] [expires: ????-??-??]

E:\>gpg --version

gpg (GnuPG) 2.2.19

libgcrypt 1.8.5

Kleopatra shows the proper expiration date: 19-Jan-38

You could use either Kleopatra itself or the Windows Explorer contextual menu - More GpgEx options for verifying the image.
https://www.gpg4win.org/doc/en/gpg4w...endium_24.html

Thanks for the heads up abga. I tried what you did and kleopatra gave me no problems of any kind. It showed the proper expiration date. I guess from now on I'll have to avoid using CMD/powershell gpg4win and use kleopatra instead. I'll mark this thread as solved.