Vagrant Cascadian wrote: > Thanks for maintaining git-remote-gcrypt! Ah drat, I forgot about this package.
It needs a Debian maintainer. I'm sort of kind of upstream for it but only because the actual upstream is not anwsering. > 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. Note that --no-tty is only supposed to be passed to gpg when there is not controlling terminal. -- see shy jo
signature.asc
Description: Digital signature
