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.
DescriptionAndreas Bleischwitz
2011-07-13 15:35:12 UTC
Description of problem:
A passphrase preseted by gpg-preset-passphrase is expired after "--max-cache-ttl" seconds although it was put into the cache with "requested tty=-1"
Version-Release number of selected component (if applicable):
gnupg2-2.0.14-4.el6.x86_64
How reproducible:
Start the agent, preset a passphrase and try to use it using gpg - this should work without questioning a passphrase.
After "max-cache-ttl" seconds try to repeat the gpg-command - this should fail or ask for a passphrase
Steps to Reproduce:
1. create gpg-key
2. eval $( gpg-agent --allow-preset-passphrase --log-file=/tmp/gpg-agent.log --debug-level=expert --sh )
3. echo "test" | gpg -ase # abort this- just for getting the keygrip
4. search for 40byte keygrip in logfile of gpg-agent
5. /usr/libexec/gpg-preset-passphrase --preset $keygrip
6. enter passphrase
7. echo "test" | gpg -ase -r <your.mailaddr>
8. sleep $max-cache-ttl
9. echo "test" | gpg -ase -r <your.mailaddr>
Actual results:
The preseted key is expired
Expected results:
The preseted key is valid forever or until SIGHUP or until --forget
Additional info:
We need the gpg-preset-passphrase funtionality for automated gpg-verify/-decryption which should not have any further user interaction
Comment 2RHEL Program Management
2011-07-13 15:58:12 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.