diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-09-11 13:39:28 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-09-11 13:39:28 -0400 |
| commit | 07aeb948f16c6dbb6a8031bf2dcaf4f6a07d2ec7 (patch) | |
| tree | e00ef29f742fbf12dfdade473bc887cfca287f1b /doc/bugs | |
| parent | b0a86d81a39f25f2e57b0e4fd564acc70cbdf850 (diff) | |
close
Diffstat (limited to 'doc/bugs')
| -rw-r--r-- | doc/bugs/cotinually_prompting_for_gpg_passphrase.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/cotinually_prompting_for_gpg_passphrase.mdwn b/doc/bugs/cotinually_prompting_for_gpg_passphrase.mdwn index 35c588055..c017cf1a6 100644 --- a/doc/bugs/cotinually_prompting_for_gpg_passphrase.mdwn +++ b/doc/bugs/cotinually_prompting_for_gpg_passphrase.mdwn @@ -63,3 +63,15 @@ error: failed to push some refs to 'gcrypt::/autofs/ext/wdpassport0/annexes/user """]] The section above I clicked cancel on the pinentry dialog as can be seen. The question is, why was it asking me anyway? + +> gpg: anonymous recipient; trying secret key 7426266D ... +> +> That means that you have git-remote-gcrypt configured to use anonymous +> recipients. This causes gpg to try a bunch of gpg keys until it finds one +> that works, rather than immediately trying the right key. +> +> I modified git-remote-gcrypt in July so you can configure +> gcrypt.publish-participants to avoid this problem. +> +> There may also be a local confguration problem; I don't know. In any +> case, it's not git-annex responsible, but git-remote-gcrypt. [[done]] --[[Joey]] |