Bug 884264

Description of problem:

In ipa we use gpg for simple symmetric encryption within a tool, basically like this:

% touch encrypt_me
% mkdir /tmp/test
% echo password | /usr/bin/gpg2 --batch --homedir /tmp/test --passphrase-fd 0 --yes --no-tty -o encrypt_me.gpg -c encrypt_me
gpg: WARNING: unsafe permissions on homedir `/tmp/test'
gpg: keyring `/tmp/test/pubring.gpg' created
gpg: can't connect to the agent: IPC connect call failed
gpg: problem with the agent: No agent running
% echo $? 2

This succeeds in encrypting the file but returns error code 2.

The reverse of this does not complain about the agent and returns 0.

% echo password | /usr/bin/gpg2 --batch --homedir /tmp/test --passphrase-fd 0 
--yes --no-tty -o encrypt_me.out -d encrypt_me.gpg
gpg: WARNING: unsafe permissions on homedir `/tmp/test'
gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
gpg: WARNING: message was not integrity protected
% echo $?
0

Similar commands works fine using gpg.

Error code 2 is not documented on the man page. It just says that anything non-zero is bad. Does 2 mean can't connect to agent or something else? I can ignore that return code if needed.

Version-Release number of selected component (if applicable):

gnupg2-2.0.19-6.el7