Why doesn't gpg-agent forwarding work?

[Stephan Beck]

Hi, (update)

Stephan Beck:
> Hi Kevin,
> 

>> Setting some environment variables in the VM does not help:
>>
>>     GPG_AGENT_INFO=/home/vagrant/.gnupg/S.gpg-agent:0:1
>>     GPG_SOCK=/home/vagrant/.gnupg/S.gpg-agent
>>     GPG_TTY=/dev/pts/1
> 
> And if you'd try to add this to the VM's .bashrc file via ssh/scp


No, positively not via ssh, as you reported that this, precisely, ssh
access is failing! So, just modifiying .bashrc manually.
> (assuming that the Vagrant's VM is headless and has a bash)
> 
> if [ -f "${HOME}/.gpg-agent-info" ]; then
>      . "${HOME}/.gpg-agent-info"
>        export GPG_AGENT_INFO
>        export SSH_AUTH_SOCK
>        export SSH_AGENT_PID
> fi
> 
> Wouldn't that start the "target shell" (forcibly) with the agent being
> fired up and all ready for sshing?
> 
> Cheers
> 
> Stephan
> 
> 
> 
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>