Currently, if a smartcard user tries to e.g. encrypt/sign a file and enters a bad PIN, the pinentry process is cancelled and the error displayed in Kleopatra:
To be able to retry, the whole encrypt/sign process has to be started again (choosing the file, etc), which is tedious.
Pinentry should handle the retries on bad PIN instead, which would also meet the user's expectation.
Split from T6425: improve pinentry behavior and texts in smart card context
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T6785 Kleopatra: Improvements related to smart cards | ||
| Open | None | T8353 Let pinentry or gnupg handle bad smartcard pins |
I don't think that Kleopatra can influence that gpg/gpgsm/gpg-agent shows a second pinentry if on the first try a wrong passphrase was entered. Therefore I think the "retry" has to be implemented in GnuPG.
Independently of this, explicit canceling of the pinentry shouldn't abort the sign/encrypt operation in Kleopatra.
So, this ticket is actually two.
I have created T8433: Kleopatra: Allow easy retry of sign/encrypt files operation if password request failed or was aborted for improving Kleopatra. This leaves the problem that entering a bad smartcard PIN (or password) aborts a sign operation without repeating the PIN/password request. I think this needs to be addressed in GnuPG. -> I re-tag this ticket and request another triage.
I guess it's fine to decide not to change GnuPG. Once Kleopatra allows for an easy retry of a sign/encrypt operation a change in GnuPG will be unnecessary for users of Kleopatra.