42

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 ?

Thomas Produit
  • 555
  • 1
  • 4
  • 7

4 Answers4

71

for those really using gpg-agent, you can forget passphrases with:

echo RELOADAGENT | gpg-connect-agent
Matija Nalis
  • 1,482
  • 15
  • 21
30

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
DrBeco
  • 491
10

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-agent to 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-agent should be running, and it does respond both to settings in ~/.gnupg/gpg-agent.conf and to SIGHUP signals.
  • 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-agent or gpg-agent
    • It's possible that your configuration for gpg-agent autostart already includes SSH support (the default one in Ubuntu 13.04 does)
Jonas Malaco
  • 1,453
  • 1
  • 13
  • 15
7
gpgconf --reload gpg-agent

This works for me ... hope this answers your question.

Koshin
  • 73