GPA - unsupported certificate

gnupg at gnupg at
Wed Dec 9 21:34:41 CET 2015

Dark Penguin wrote:

> > > maybe it would make sense to disregard GPG_AGENT_INFO if it points to
> > > GNOME Keyring one, or maybe even disregard it always, or maybe even
> > > have GPA use another fixed path to always connect to "our"
> > > gpg-agent?
> >
> > GnuPG 2.1 already always uses a fixed path and disregards the variable.
> > And recent GnuPG 2.0 versions already warn about the hijack. The problem
> > is that two software projects want opposite things; this would lead to
> > an arms race. But fortunately, it will all go away when distributions
> > start using recent versions of the software, as the issue has finally
> > been resolved.
> Ok, so now it's only a question of GPA and GnuPG 2.1 being backported to
> Jessie. That's good to know.

Does this mean that gpg-agent's --write-env-file option has
also been removed in 2.1? I'm relying on that and had better
be paying attention when gpg gets upgraded on my systems so
I can change my scripts to keep them working.


More information about the Gnupg-users mailing list