error return code when no agent available

Andreas Stieger astieger at
Thu Nov 30 13:26:17 CET 2017


In GnuPG 2.2.x we see the following when compared to 2.0.x:

* no gpg-agent binary available
* no gnupg home directory created and no keyrings
* gpg --import a random public key
* The public key import succeeds in both cases, but 2.2.x returns with
an exit code of 2.

CLI is:

/usr/bin/gpg2 --import --homedir /var/tmp/RAMDOM --no-default-keyring
--quiet \
--no-tty --no-greeting --no-permission-warning --status-fd 1 /var/tmp/KEY

The return code of 2 seems to depends specifically on the availability
of an agent binary. This is a minimal installer system where no agent is
available or required due to the lack of private key operations.
Previously this was not an issue. Do you know what and why this changed?
If this is intentional, is there a work-around in terms of settings or
the CLI?

Our bug:


Andreas Stieger <astieger at>
Project Manager Security
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Gnupg-devel mailing list