summaryrefslogtreecommitdiff
path: root/plugins/gpg-agent
AgeCommit message (Collapse)Author
2013-07-15PLUGIN: gpg-agent: export SSH_* environment variables tooSukant Hajra
If using the gpg-agent with --enable-ssh-support, the SSH_AUTH_SOCK and SSH_AGENT_PID environment variables need to be exported once sourced from GPG_ENV. Otherwise, we get no benefit from the persisting these values to GPG_ENV; subsequent openned terminals don't see the existent gpg-agent as a process for an SSH daemon.
2013-07-11fix gpg-agent "running already" checkSukant Hajra
The GPG_ENV file is sourced before doing the gpg-connect-agent check, but this file (unlike the SSH_ENV file) doesn't export GPG_AGENT_INFO, so the check always fails. This results in new gpg-agents continuously being spawned. All this commit does is put in the single export to fix the problem.
2013-06-23TypoOlaf Conradi
2013-06-23Prevent starting multiple gpg-agentsOlaf Conradi
Don't just overwrite the environment. First check for a running agent (an x-session might have one running). If no agent is found, source the environment and check again using those settings. If again no agent is found, start a new instance.
2013-02-21Added --quiet to suppress message about gpg-agent already running.Heiko Reese
2013-02-21Disable ssh-agent support if another ssh-agent is already running.Heiko Reese
2010-10-15Added gpg-agent pluginFlorian Walch
Based on ssh-agent plugin.