[Gpg4win-users-en] "Certificate expired" still happens after GnuPG is updated to 2.2.32

Yasuhiro Kimura yasu at utahime.org
Tue Oct 19 18:06:54 CEST 2021


Hello,

I read following announce.

https://lists.wald.intevation.org/pipermail/gpg4win-announce/2021-October/000093.html

According to it I downloaded gnupg-w32-2.2.32_20211006.exe and
installed it over Gpg4win 3.1.16.

----------------------------------------------------------------------
C:\Users\yasu>gpg --version
gpg (GnuPG) 2.2.32
libgcrypt 1.8.8
Copyright (C) 2021 g10 Code GmbH
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: C:/Users/yasu/AppData/Roaming/gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

C:\Users\yasu>
----------------------------------------------------------------------

But `gpg --search-keys` still results in "Certificate expired".

----------------------------------------------------------------------
C:\Users\yasu>gpg --search-keys gmail.com
gpg: error searching keyserver: Certificate expired
gpg: keyserver search failed: Certificate expired

C:\Users\yasu>
----------------------------------------------------------------------

What's wrong? My environment is Windows 10 21H1.

Best Regards.

---
Yasuhiro Kimura


More information about the Gpg4win-users-en mailing list