Hide Forgot
Description of problem: Operations of gpgsm fail because it is not possible to connect to running gpg-agent. Version-Release number of selected component (if applicable): gnupg2-2.0.22-4.el7 How reproducible: Steps to Reproduce: 1. gpgsm --verbose --disable-crl-checks --disable-ocsp --debug-ignore-expiration --cipher-algo 3DES -e binary.msg -r <recipient> -o binary.msg-3DES 2. 3. Actual results: test> pgrep gpg-agent test> gpgsm --verbose --disable-crl-checks --disable-ocsp --debug-ignore-expiration -r 3C:F4:05:46:4F:66:ED:4A:7D:F4:5B:BD:D1:E4:28:2E:33:BD:B7:6E -o binary.msg-3DES --cipher-algo 3DES -e binary.msg gpgsm: no key usage specified - assuming all usages gpgsm: no running gpg-agent - starting one gpgsm: waiting 5 seconds for the agent to come up gpgsm: can't connect to the agent: Invalid value passed to IPC gpgsm: certificate has expired gpgsm: (expired at 2002-12-03 09:36:38) gpgsm: WARNING: ignoring expiration gpgsm: checking the trust list failed: No agent running gpgsm: validation model used: shell gpgsm: can't encrypt to `3C:F4:05:46:4F:66:ED:4A:7D:F4:5B:BD:D1:E4:28:2E:33:BD:B7:6E': No agent running test> pgrep gpg-agent 6366 test> gpgsm --verbose --disable-crl-checks --disable-ocsp --debug-ignore-expiration -r 3C:F4:05:46:4F:66:ED:4A:7D:F4:5B:BD:D1:E4:28:2E:33:BD:B7:6E -o binary.msg-3DES --cipher-algo 3DES -e binary.msg gpgsm: no key usage specified - assuming all usages gpgsm: no running gpg-agent - starting one gpgsm: waiting 5 seconds for the agent to come up gpgsm: can't connect to the agent: Invalid value passed to IPC gpgsm: certificate has expired gpgsm: (expired at 2002-12-03 09:36:38) gpgsm: WARNING: ignoring expiration gpgsm: checking the trust list failed: No agent running gpgsm: validation model used: shell gpgsm: can't encrypt to `3C:F4:05:46:4F:66:ED:4A:7D:F4:5B:BD:D1:E4:28:2E:33:BD:B7:6E': No agent running Expected results: Additional info: It looks like it was never worked on RHEL7. On the other hand, on RHEL6 it works just fine.
*** Bug 1374741 has been marked as a duplicate of this bug. ***
As there is no customer case attached, I am going to close this request.