Hide Forgot
Description of problem: Given a file '/root/somefile.gpg' that has been encrypted via gpg with passphrase 'asdfg' issue the following decrypt request at the command line, without seahorse operational. gpg -d --passphrase 'asdfg' '/root/somefile.gpg';echo Return Code=$? This will work. Now try the same thing with seahorse running and you'll note that the --passphrase option is ignored as seahorse-tool pops up and takes control. This means there's no way to script gpg executions that don't rely on console input. If the passphrase is overtly supplied on the command line, seahorse-tool should never show up. BTW - seahorse-tool consumes nearly 100% cpu if you double click a gpg file from within nautilus.
This issue is with any of the key managers that attempt to intercept passphrase functionality. Executing gpg -d --passphrase 'asdfg' '/root/somefile.gpg';echo Return Code=$? from a terminal session WITHOUT a GUI works just fine. Executing it within a GUI but unsetting GPG_AGENT_INFO also works fine. Executing it within a GUI with GPG_AGENT_INFO set as the default, causes the trouble. I uninstalled seahorse, and it still happens, with something intercepting the passphrase function, and I think its gnome keyring but I'm not sure. What ever is setting GPG_AGENT_INFO is probably responsible. The --pass-repeat option is also ignored when the GUI is available.
Just a quick hint: You need to use --batch with gpg if you don't want a user interaction.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.