Decryption stalling after SIGINT

[Werner Koch]

On Tue,  7 Jul 2020 18:05, Andrew Pennebaker said:
> I am seeing some strange behavior with gpg --decrypt <path>. I had to
> lookup a password recently, and so naturally pressed Control+C to cancel
> the prompt. However, when gpg terminated, it did not fully cleanup the

This will terminate gpg and thus the connection to gpg-agent.  However,
depending on the type of the pinentry it may happen that the pinentry is
still active and you did not notice that.  It will eventually time out
and a new pinentry can come up; a complete deadlock should not happen,
even not on macOS.

Please run the gpg commands with option --verbose so you should be
notified about active pinentries; for example:

  gpg: pinentry launched (5591 gtk2 1.1.1-beta29 /dev/pts/123 xterm [...]

If this does not reveal anything add

  --debug ipc

to the gpg invocation and you will see the communication between gpg and
gpg-agent and possible with dirmngr (for network actions).


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20200709/f8147426/attachment.sig>