Hide Forgot
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
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.