Don't get the pinentry for passphrase in some contexts

Werner Koch wk at
Thu Jul 13 16:06:08 CEST 2017

On Thu, 13 Jul 2017 15:08, damien at said:
> strace reveals the following. Does that ring a bell to anyone?

"debug-pinentry" in gpg-agent.conf would give you more info.  Adding
also "debug ipc" will show you the communication between gpg and
gpg-agent; that is what you strace shows.  Use "log-file FILE" to set a
log file and remember to reload gpg-agent.

> In Firefox
>     read(5, "INQUIRE PINENTRY_LAUNCHED 22712\n", 1002) = 32
>     write(5, "END", 3)                = 3
>     write(5, "\n", 1)                 = 1

The agent tells gpg that a pinentry has been launched and gpg
acknowledges that ("END").

>     read(5, "ERR 83886179 Operation cancelled <Pinentry>\n", 1002) = 44

The agent tells you that the Pinentry canceled the operation.  This is
usually due to clicking the cancel button.  Some older versions of
pinentry use cancel as a catch all error from pinentry.  Modern versions
of gpg running with "-v" will print a line identifing the pinentry used
and thus reveal possible problems, for example a missing GPG_TTY
envrionment variable.

>     read(5, "D (5:value511...) = 543

This returns some data ;-)



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: </pipermail/attachments/20170713/33022fda/attachment.sig>

More information about the Gnupg-users mailing list