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
That'll do it! Thanks.
On 10/19/2016 02:22 PM, Daniel Kahn Gillmor wrote:
> Hi Kevin--
>
> On Wed 2016-10-19 12:45:42 -0400, Kevin Gallagher wrote:
>> I've been seeing this error lately both with one of my local GPG
>> keyrings, and with apt.
>>
>> gpg: [do
I've been seeing this error lately both with one of my local GPG
keyrings, and with apt.
gpg: [don't know]: invalid packet (ctb=2d)
gpg: keydb_get_keyblock failed: Value not found
gpg: [don't know]: invalid packet (ctb=2d)
gpg: /tmp/tmp.rObzKgJEj5/pubring.gpg: copy to
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
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
