Page MenuHome GnuPG

Kleopatra: "General Error" is given instead of "Wrong PIN"
Testing, NormalPublic


On key creation via "Generate New Keys" in the smart card tab:
Enter the Admin PIN correctly and then give a wrong User PIN. This results in "General Error"

But scdaemon "knows" that it was the wrong PIN:

4 - 2024-01-30 16:27:28 scdaemon[9152]: Pr�fung des CHV2 fehlgeschlagen: Falsche PIN
4 - 2024-01-30 16:27:28 scdaemon[9152]: operation check_pin result: Falsche PIN
4 - 2024-01-30 16:27:28 scdaemon[9152]: app_check_pin failed: Falsche PIN
4 - 2024-01-30 16:27:28 scdaemon[9152]: DBG: chan_0x000003d8 -> ERR 100663383 Falsche PIN <SCD>

This is similar to T6182, which was (and is still) fixed


noticed on VSD 3.2.2 beta

Event Timeline

aheinecke triaged this task as Normal priority.Feb 7 2024, 9:14 AM
aheinecke added a subscriber: aheinecke.

Yes that probably gets lost along the way, where we communicate with scdaemon to generate the key. Needs to be tracked down. Such things can be very confusing to users. Especially if that increases the PIN Retry counter!

The General Error happens also when the PIN is blocked and no Pinentry opens.
As in this case, where the indicated "Generate New Keys" button was used on a blocked card.

ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.

Fixed (for GnuPG 2.4). I hope 2.2 prints the same status messages.

Oops. I closed the task accidentally.