How to prevent passphrase-caching from within a gpgme-based Python script?

[Peter Lebbing]

On 16/04/2019 23:23, Ángel wrote:
> Of course, you could instead run gpg-agent from python and set
> GPG_AGENT_INFO there. The gpg python package is calling gpg under the
> hood, so it should pick the GPG_AGENT_INFO variable from the
> environment.

GPG_AGENT_INFO is obsolete and unused in GnuPG 2.1+ (and GnuPG 2.0 is
obsolete itself :-). So I'm afraid that won't work.

The agent and the homedir are tightly coupled. If you want to do
something special to the agent, I think you're going to have to go the
undesirable route of a separate homedir...

HTH,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20190416/941f6e25/attachment.sig>