Wed, Nov 19
Sun, Nov 16
Fix applied. Thanks.
Fri, Nov 14
Thu, Nov 6
Oct 9 2025
Might this be related to T4953?
Oct 6 2025
(auto resolved due to the keyword "resolved" in the commit message)
The window was not reenabled on failure see 8d174d5
Oct 2 2025
(removed: wrong statement)
Note: I also activated Sign/Encrypt by default, if that matters
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.
Aug 27 2025
The problem here is that we don't have the sha-2 fingerprint in our SQL tables. Thus we would not only need to do a full table search but also parse the actual blob to compute the sha-2 fingerprint.
I have done testing using my QES certificate with all combinations of the two options.
Jul 25 2025
Jul 24 2025
This does not happen with gnupg24 because the cache has not been implemented there.
Jul 2 2025
May 13 2025
Meanwhile we have some support for an empty subject but gpgsm still prints an error notice. See the T7171 for more.
Apr 22 2025
BTW, fingerprints for X.509 are not well defined because you get a different one when changing the *unsigned" attributes. Not a common case but one should be aware of it.
Feb 18 2025
Jan 24 2025
If you encounter real world certificates with these parameters we can bump up the priority.
Jan 19 2025
I think I can understand you, too much complexity.
Jan 17 2025
See this comment which is related to T4538:
Jan 7 2025
Also works in VSD-beta-478
