Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1030522

Summary: using gpg starts gpg-agent, but GPG_TTY not set -> unable to type passphrase on an ssh connection
Product: Red Hat Enterprise Linux 7 Reporter: Paolo Bonzini <pbonzini>
Component: gnupg2Assignee: Tomas Mraz <tmraz>
Status: CLOSED NOTABUG QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: somlo
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-13 15:47:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paolo Bonzini 2013-11-14 15:48:05 UTC
Description of problem:
gpg 

Version-Release number of selected component (if applicable):
gnupg2-2.0.22-1.el7.x86_64
pinentry-0.8.1-10.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Log in to a RHEL7 machine via ssh
2. echo abc | gpg -bsau 'Paolo Bonzini <pbonzini>'

Actual results:
You need a passphrase to unlock the secret key for
user: "Paolo Bonzini <pbonzini>"
4096-bit RSA key, ID 9B4D86F2, created 2013-03-07

gpg: problem with the agent: No pinentry
gpg: skipped "Paolo Bonzini <pbonzini>": Operation cancelled
gpg: signing failed: Operation cancelled

Expected results:
pinentry-curses comes up and asks for a passphrase

Additional info:
Doing "export GPG_TTY=`tty`" from the command line makes it work.

Comment 2 Gabriel Somlo 2014-01-05 17:48:18 UTC
I noticed the same behavior on Fedora 20 while attempting to decrypt something for the first time using

cat foo | gpg -d

Using

gpg -d foo

instead works fine; subsequent attempts to decrypt work using either syntax, once the agent is running and has the passphrase.

Also, Paolo's workaround (setting GPG_TTY) helps, thanks for that !

Comment 3 Tomas Mraz 2014-01-13 15:47:34 UTC
Well this is expected and setting the GPG_TTY is what you should do if you need to redirect gpg input.