gpg-agent, pinentry and Emacs

Werner Koch wk at
Mon Nov 25 16:56:56 CET 2019

On Mon, 25 Nov 2019 08:44, Werner Koch said:

> Thanks.  I don't see that INSIDE_EMACS is propagated and I can duplicate

My fault.  We pass the the envvars to pinentry using setnev in an atfork
handler.  Thus we do not see them in the Assuan log.  I added some
logging to so that we can now see without a wrapper which envvars care
send to pinentry.

In my tests INSIDE_EMACS is set if I set it before calling gpg;
regardless of whether the agent is running or not.  Thus the problem is
not in gnupg but may be in pinentry or the emacs code calling gpg.



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: <>

More information about the Gnupg-users mailing list