Ok, I figured out the cause of the problem I was having. As is indicated
in your message, one must have the corresponding public keys in the
remote keyring before the secret keys from the forwarded gpg-agent are
listed as available.
Thank you Thomas. I hope others will find this useful.
On
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
Hi Kevin,
Kevin Gallagher:
> Hi all,
>
> I've tried to get this working to no avail. I've consulted past postings
> to this list as well as various online references. Some people seem to
> have got this to work, but most seem to have trouble. I would appreciate
> any guidance or help anyone can
Hello Kevin,
> Thanks for the advice. But as I mentioned, I tried using GnuPG 2.1.15
> on the target machine as well (via the packages in Debian sid), and
> this did not work. gpg2 is simply not speaking to the forwarded
> gpg-agent socket, however gpg-connect-agent can. Any other ideas?
Check
Hey Thomas,
Thanks for the advice. But as I mentioned, I tried using GnuPG 2.1.15 on
the target machine as well (via the packages in Debian sid), and this
did not work. gpg2 is simply not speaking to the forwarded gpg-agent
socket, however gpg-connect-agent can. Any other ideas?
Kevin
On
Hello Kevin,
> GPG version on host: 2.1.15 (Debian stretch)
> GPG version on VM: 2.0.26 (Debian jessie)
gpg 2.0.26 does the gpg operations local and not using gnupg-agent.
Starting with the 2.1.x versions gnupg uses gnupg-agent for doing all
operations. As a result you need to have 2.1.x on the
Hi all,
I've tried to get this working to no avail. I've consulted past postings
to this list as well as various online references. Some people seem to
have got this to work, but most seem to have trouble. I would appreciate
any guidance or help anyone can offer.
I want my gpg-agent to be shared
