On 2014-11-25, Joey Hess wrote: > Vagrant Cascadian wrote: >> When attempting to connect to a remote, I get the following... >> >> git remote update >> Fetching origin >> + [ x/run/user/1000/keyring/gpg:0:1 != x ] >> + gpg --no-tty --armor --gen-rand 1 9 >> + set +x >> gcrypt: Development version -- Repository format MAY CHANGE >> gcrypt: Decrypting manifest >> + [ x/run/user/1000/keyring/gpg:0:1 != x ] >> + gpg --no-tty --status-fd 3 -q -d >> gpg: anonymous recipient; trying secret key 0123456789ABCDEF ... >> gpg: Sorry, no terminal at all requested - can't get input >> gcrypt: Failed to decrypt manifest! >> error: Could not fetch origin >> >> I don't understand why it doesn't use GPG_AGENT_INFO ... other >> programs have no trouble using it. I don't think there's any >> particularly strange configuration on my part... >> >> If I unset GPG_AGENT_INFO it prompts me directly multiple times, but >> does work... if I add --use-agent it also works, so here's a patch to >> try that, not sure if it has other consequences: > > I guess I'd worry this would make it not work when there is no agent.
Sure, that makes sense. I stumbled upon a similar issue with obnam: https://bugs.debian.org/649769 Apparently, adding "use-agent" to my gpg.conf fixes the issue for both git-remote-gcrypt and obnam... at least that's a viable workaround. Ideally, git-remote-gcrypt would detect which to use, but maybe a commandline option and/or environment variable that allowed the user to pass gpg arguments would be worth implimenting? live well, vagrant
signature.asc
Description: PGP signature
