On Tue, 25 Aug 2015 23:29, t...@mirbsd.de said: > since one of the recent upgrades, gpg-agent no longer writes its > environment file. This is a rather bad regression for my setup,
Rignt, that is because it is not anymore used except for ssh. See the man page. Here is what I have in my profile (.bashrc in my case) for ages (eben 2.0 could be configured or started with a fixed socket) --8<---------------cut here---------------start------------->8--- if [ "$PS1" ]; then # Setup information required by GnuPG and ssh. We use the # standard socket in GnuPG's homedir, thus there is no need for an # environment variable. We reset any left over envvar. # SSH_AGENT_PID should not be set because it is only used # to kill ssh-agent (option -k) but we don't want this to kill # gpg-agent. Because ssh does not know about GnuPG's homedir we # need to set its envvar to the standard of gpg-agent. GPG_TTY needs # to be set to the current TTY. The extra test is used to avoid # setting SSH_AUTH_SOCK if gpg-agent has been started with the # shell on the command line (often used for testing). unset GPG_AGENT_INFO unset SSH_AGENT_PID if [ "${gnupg_SSH_AUTH_SOCK_by:-0}" -ne $$ ]; then export SSH_AUTH_SOCK="${HOME}/.gnupg/S.gpg-agent.ssh" fi fi export GPG_TTY=`tty` --8<---------------cut here---------------end--------------->8--- Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.