I've tried:
- the SIGHUP method --> no succes
- the cache timeout in gpg-agent.conf --> it seems that this file is not read, althougt I have the 'use-agent' line in gpg.conf
What should I do ?
asked Sep 23, 2013 at 21:31
4 Answers
for those really using gpg-agent, you can forget passphrases with:
echo RELOADAGENT | gpg-connect-agent
-
3Thank you! That works just fine for
gnome-keyring-daemontoo (on 14.04) - I've looked everywhere to find a simple "forget"!– GregFeb 5, 2015 at 13:03 -
-
1Thank you very much for this simple and effective "forget" tool. All the methods discussed above regarding how to manage caching of gpg passwords misses the fundamental point that we should never ever allow passwords to be cached in the first place.– user587469Jul 12, 2017 at 20:47
-
1Note that this does not clear your password from memory. Gpg-agent will prompt you again, pretending it has forgotten, but it hasn't. I assume people want to clear the cached password to protect against an attacker that can invoke gpg-agent or read the memory, but if an attacker can invoke gpg-agent (because your laptop is unlocked) or get your RAM (because you're out for lunch), they can also just get the password from memory or wrap the pinentry program to capture it.– LucMar 5, 2020 at 14:49
-
1
GPG: In a single command:
gpg-connect-agent reloadagent /bye
SSH: for ssh agent you probably want those two:
ssh-add -D #delete identities
ssh-agent -k #kill ssh-agent
-
2I wonder why they did not make this easier using gpg itself. Example:
gpg --clear-password-cache– MaXi32Mar 9, 2021 at 16:49
Let me begin by saying I had the exact same issue...
Your GPG secrets are probably being handled by the Gnome Keyring, even if gpg-agent is running. This answer provides some details on the available options for it.
Another way is to disable the GPG component of the Gnome Keyring, so that gpg-agent is used:
- You can do this by removing (or renaming to something other than
*.desktop) the file/etc/xdg/autostart/gnome-keyring-gpg.desktop. - It's possible you already have the necessary settings for
gpg-agentto autostart. At least for me, running Ubuntu 13.04, that's true. However, if you need to, refer this post for some information on how to configure it. - After logging off and on again, just
gpg-agentshould be running, and it does respond both to settings in~/.gnupg/gpg-agent.confand toSIGHUPsignals. - On a final note, it may be wise to also disable the SSH component of Gnome Keyring, since:
- You probably also don't want your SSH keys unlocked for the whole session, and might want to use/configure
ssh-agentorgpg-agent - It's possible that your configuration for
gpg-agentautostart already includes SSH support (the default one in Ubuntu 13.04 does)
- You probably also don't want your SSH keys unlocked for the whole session, and might want to use/configure
answered Nov 23, 2013 at 14:36
-
I'm struggling with this issue. Under Ubuntu 18.04 the
gnome-keyring-gpg.desktopfile does not exist.– LinterAug 10, 2018 at 13:58
gpgconf --reload gpg-agent
This works for me ... hope this answers your question.
gpg-agent.conffile. So I want to ask: what is your GPG agent? Are you sure it is confgured properly? Where are you sending SIGHUP?gpg-connect-agentdoes indeed seem to work for seahorse (at least for me on 14.04), not justgpg-agent. This means that without disablinggnome-keyringyou should be able to use it out of the box.