Package: gnupg2
Version: 2.1.0~beta895-2
Severity: normal
Hi!
The way the new xsession file works, the SSH_AGENT environment
variables are no longer exported from gpg-agent. As a result, ssh
can'tcontact gpg-agent and ssh-agent is started by its own (it runs
after gpg-agent's xsession thing
Ahoi!
setting SSH_AGENT_PID and SSH_AUTH_SOCKET to ~/.gnupg/S.gpg-agent.ssh if
it exists should be enough fwiw. It even then supports ed25519 keys (wrt
#764702)
Christoph
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Control: tags 767341 + patch
Hi Christoph--
On Thu 2014-10-30 07:06:47 -0400, Christoph Egger wrote:
setting SSH_AGENT_PID and SSH_AUTH_SOCKET to ~/.gnupg/S.gpg-agent.ssh if
it exists should be enough fwiw. It even then supports ed25519 keys (wrt
#764702)
I don't want to auto-enable that
Hi!
Daniel Kahn Gillmor d...@fifthhorseman.net writes:
On Thu 2014-10-30 07:06:47 -0400, Christoph Egger wrote:
setting SSH_AGENT_PID and SSH_AUTH_SOCKET to ~/.gnupg/S.gpg-agent.ssh if
it exists should be enough fwiw. It even then supports ed25519 keys (wrt
#764702)
I don't want to
4 matches
Mail list logo