in Gpg4win-5.0.0-beta479

Yubikeys allow that. See my mail to the mailing list.

Seems like the OpenPGP Card Specification does not allow the change of retry counters.

Fix applied. Thanks.

That's what gpg-card url --clear does

if (!strcmp (argstr, "--clear"))
  url = xstrdup (" "); /* No real way to clear; set to space instead. */

So we need to find out what gpg-card url --clear does to avoid the card error for the ZeitControl cards.

Note: It works with gpg-card url --clear.

I could reproduce this with a ZeitControl OpenPGP v3.4 card, but (as Tobias) not with an (old) Yubikey. Looks like a bug in the card firmware.

@gniibe: Now that we use the KEM API, how do we proceed with this ticket?

The actual project we had in mind for this was more or less canceled and thus I re-prioritize this task.

Reminder mostly to self: This is about the KDF parameters. In the light of PQC composite algorithms we may want to also prepare for PQC required stuff.

A brief update: This feature has not made it onto the roadmap of specific things to implement so far.

This might also be related to rGa7ec3792c5 (cf. T2982)

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

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.

Fixed in 2.5.2.

Fixed in 2.5.0 and 2.4.6.

Fixed in 2.5.0 and 2.4.6.

Fixed in 2.4.6.

I believe this was fixed by T7386. Or it is now no hard lock up by T7402.
So, let me close this ticket.
If any new symptom, please add information into T7396.

I can say it's fixed in 2.4.7.

In select_application function, we can minimize the holding W-lock.

This may requires major changes for scdaemon.