Running the agent --debug 4096 --debug-level guru --daemon --min-passphrase-len 0
$ ssh my-vm
gpg-agent[29336]: ssh handler 0x for fd 8 started
gpg-agent[29336]: ssh request handler for request_identities (11) started
gpg-agent[29336]: ssh request handler for request_identities (11)
On Thu, Jun 22, 2017 at 07:05:38PM +0200, Werner Koch wrote:
> SSH_AUTH_SOCK="$(gpgconf --list-dirs agent-ssh-socket)"
> export SSH_AUTH_SOCK
>
> is the way to go.
thanks for tip
> Right. gpg-agent takes a copy of the key and stored it in its own DB.
good to know
But still, that's
On Tue, 20 Jun 2017 07:09, raphael.d...@gmail.com said:
> $ eval $(gpg-agent --enable-ssh-support)
Please don't do that anymore.
SSH_AUTH_SOCK="$(gpgconf --list-dirs agent-ssh-socket)"
export SSH_AUTH_SOCK
is the way to go.
> automatically provides two of my keys. ssh-add -D does not seem
Just upgraded from Jessie to Stretch, same issue.
This used to just work
$ eval $(gpg-agent --enable-ssh-support)
But ssh connections now fail miserably.
I'm offered the ssh key pinentry popup, and then:
> sign_and_send_pubkey: signing failed: agent refused operation
I also tried to kill all
Package: gnupg-agent
Version: 2.1.14-5
Severity: minor
Dear Maintainer,
Since the upgrade to the newest gnupg-agent I had the problem that
gnupg-agent just refused any ssh agent work with a simple
sign_and_send_pubkey: signing failed: agent refused operation
which isn't all that helpful a
5 matches
Mail list logo
