This is a milestone - please do not use. Use the standard gnupg tag and describe which versions are affected.
Details
Yesterday
For command line, reported issues have been fixed; Confusions for wrong errors are gone, it correctly reports appropriate errors of:
- GPG_ERR_PIN_BLOCKED
- GPG_ERR_NO_RESET_CODE
- GPG_ERR_BAD_PIN
Mon, Jan 20
What is the status (or maybe better scope) of this ticket? Why was it set to the milestone 2.4.5?
I do not see any improvement in Kleopatra from Gpg4win 4.4 (with gpg 2.4.7) regarding the behavior when trying to unblock a card.
Nov 19 2024
@ebo i'm not sure i understand why you removed the gnupg24 (gnupg-2.4.5) project label. the report indicates that GnuPG 2.4.6 at least (other versions untested, but i didn't see a gnupg24 (gnupg-2.4.6) label in this system) produces MPI artifacts for EdDSA/Ed25519 signatures that are non-compliant with all the known specifications. the 2.2 series appears to retain compatible MPI formats.
Nov 18 2024
after a bit more testing, it looks to me like 2.2.45 will revise the signature packet to use 0x00ed as the MPI header for r, if it receives input from 2.4.6. And 2.4.6 will revise the signature packet to use 0x0100 as the MPI header for r. So the same OpenPGP self-sig will change shape each time it is passed back and forth between the different versions.
Oct 4 2024
We won't fix that for 2.2.