Thu, Dec 18
Well, I tested this again. I created a new key and saved a copy. The I updated the expiration date to 2035 and sent the key to the LDAP server. Then I deleted the updated key locally and imported the old copy. Thus I have now:
Fri, Dec 12
we haven't seen this in a while…
Fri, Dec 5
Thu, Dec 4
Fri, Nov 28
This seems not to work in Kleopatra/gpg in gpg4win-5.0.0-beta413 @ win11.
Thu, Nov 27
Tested on gpg4win-5.0.0-beta413 @ win11 with the following entries in dirmngr.conf:
Fri, Nov 21
Nov 19 2025
Nov 18 2025
Nov 16 2025
Nov 14 2025
Nov 13 2025
meanwhile it looks like this in Kleopatra, it has now the blue sign but the issue is still the same:
Nov 5 2025
Nov 3 2025
Oct 23 2025
Looks good to me on gpg4win-5.0.0-beta395 @ win11 (gpg 2.5.13).
Oct 22 2025
Oct 21 2025
Oct 13 2025
Oct 9 2025
Oct 7 2025
We recently noticed problem at a customer site with creating the standard rsa3072 keys. It basically stopped working. A likely cause for this seems to be some anti-malware software slowing down file system calls. In the wake of this we looked again at our file locking strategy and found a few things which are not as they should be. For example the release of the lock before a Close call. Trying to fix this unfortunately caused other problems, thus a couple of fixes are needed.
Oct 2 2025
Sep 24 2025
ECC support for X.509 and in particular pkcs#12 format is limited. That is in general not a problem because such certificates are stored on a token and not on disk.
Also implemented for 2.2
Will be backported after 2.2.49
Tested with VS-Desktop-3.3.90.12-Beta
Sep 23 2025
2.2 test can be done with GnuPG-VS-Desktop-3.3.90.12-Beta-Standard.msi from Sep 17
