[issue37] Cancelling pinentry not propagated back to the application
Marc Mutz
aegypten-issues at intevation.de
Fri Jan 16 14:34:59 CET 2004
New submission from Marc Mutz <marc at klaralvdalens-datakonsult.se>:
When cancelling a pinentry passphrase prompt, gpg-agent correctly notices this:
gpg-agent[21542.0x8062f08] DBG: <- PKSIGN
<snip>
2004-01-16 15:24:13 gpg-agent[21542] DBG: ... miss
2004-01-16 15:24:14 gpg-agent[21542] DBG: connection to PIN entry established
2004-01-16 15:24:15 gpg-agent[21542] failed to unprotect the secret key:
Operation cancelled
<snip>
However, what gets reported back to gpg(sm) and thus to the application is
this:
2004-01-16 15:24:15 gpg-agent[21542] failed to read the secret key
2004-01-16 15:24:15 gpg-agent[21542] command pksign failed: No secret key
gpg-agent[21542.0x8062f08] DBG: -> ERR 67108881 No secret key <GPG Agent>
gpg-agent[21542.0x8062f08] DBG: <- [EOF]
----------
messages: 118
nosy: marc
priority: bug
status: unread
title: Cancelling pinentry not propagated back to the application
topic: gpg-agent, pinentry
______________________________________________________
Aegypten issue tracker <aegypten-issues at intevation.de>
<https://intevation.de/roundup/aegypten/issue37>
______________________________________________________
More information about the Gpa-dev
mailing list