On Thu, 13 Jul 2017 15:08, dam...@cassou.me 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 ;-)
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpBLo6tkmhZU.pgp
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
