Tue, Mar 3
It seemed that the reporter (also) claimed that a git repo could be weak/vulnerable when X.509 signature is used to validate the commits.
For the record (to show we don't hide a problem), I add some information.
Mon, Feb 23
Fri, Feb 20
Applied the change in: rK86c6e972421a: Fix a memory leak in _ksba_ber_decoder_decode.
Wed, Feb 18
Tue, Feb 17
Looks like this spot was missed when T5037: dn.cpp:181: suspicious loop was fixed. In libkleo's copy of the DN parser I applied the fix in 2023. Too many copies!
Mon, Feb 16
I found a possible leak and a possible access of freed memory.
Fri, Feb 13
Jan 29 2026
Jan 23 2026
Jan 21 2026
Jan 16 2026
See the gnupg-devel mailing list for more discussions. Subject: libgcrypt P256 signature malleability via weak DER enforcement"
Jan 14 2026
Some historic integer encoding glitches from Peter Gutmann's style guide:
May 20 2025
Please review the patch and feedback.
May 13 2025
Apr 23 2025
Jan 17 2025
Jan 15 2025
Dec 5 2024
A workaround exists with the new option --ignore-crl-extensions.
Oct 29 2024
Jun 21 2024
Now also done for libksba.
Jun 20 2024
Feb 29 2024
Fixed in libksba 1.6.6.
Feb 23 2024
Feb 14 2024
@Jakuje, you are right. This is a plain error and we should do a new release to avoid false errors.
Thank you, applied.
