If I hit "Cancel" in the pinentry window the behavior is the same as hitting "OK" -> the second pinentry window comes up.
After hitting "Cancel" again an error window comes up:
The message seems to depend on the input given to the first pinentry window.
I would expect that the second pinentry window would be skipped when choosing "Cancel".
Additionally I'd expect a more userfriendly error messages in both cases.
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRAef22a58c8ca8 Treat empty result without error as canceled secret key export job | |||
| rKLEOPATRAf3866184e841 Treat empty result without error as canceled secret key export job | |||
| rKLEOPATRA65e8a1651191 Port paperkey command away from GnuPGProcessCommand | |||
| rKLEOPATRA54fa5efb5e21 Port paperkey command away from GnuPGProcessCommand | |||
| rKLEOPATRAf7ae4129f506 Port paperkey command away from GnuPGProcessCommand | |||
| rKLEOPATRAb4b995d59e3c Port paperkey command away from GnuPGProcessCommand | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Testing | • TobiasFella | T6091 Kleopatra: "Cancel" in the password dialog of "Print secret key" has no effect | ||
| Open | None | T7373 gpg --export-secret-keys exits with General error if the password prompt was canceled | ||
| Open | None | T7374 gpgme: The export operation seems to ignore failures reported by gpg |
The command needs to be ported away from running gpg --export-secret-key via QProcess to using QGpgME::ExportJob. I'll give this a low priority.
This has also been reported at https://bugs.kde.org/show_bug.cgi?id=477798 (although there a crash occurs). Porting the command to gpgme didn't help, but the remaining problems are in gpg and/or gpgme.
gpg doesn't properly report the cancelation via a status log and therefore gpgme has no idea that the operation was canceled. -> subtask T7373: gpg --export-secret-keys exits with General error if the password prompt was canceled
And the General error that gpg emits via a failure status log seems to ignored by gpgme so that the error handling in Kleopatra cannot handle this error. -> subtask T7374: gpgme: The export operation seems to ignore failures reported by gpg
Canceling the password prompt is now handled correctly, i.e. the operation is aborted without further feedback.