summaryrefslogtreecommitdiff
path: root/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-01-16 15:27:46 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-01-16 15:27:46 -0400
commit643bb4a3e1494e35f276c5aa789ebecb2127f79f (patch)
treef8697dcb0fc4e4418d37bdb5f206f4660d8a98d5 /doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn
parentff469c1d5e41764651869e8dc2f0322257811a7a (diff)
Deal with incompatability in gpg2, which caused prompts for encryption passphrases rather than using the supplied --passphrase-fd.
Diffstat (limited to 'doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn')
-rw-r--r--doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn b/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn
index 10be47679..e6f3524b2 100644
--- a/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn
+++ b/doc/bugs/With_S3__44___GPG_ask_for_a_new_passphrase.mdwn
@@ -15,3 +15,7 @@ So I create a new passphrase (two times) for each file I tried to upload. The pr
What's this new passphrase for?
BTW: git-annex version: 3.20130102 same precompiled binary on Arch Linux.
+
+> I've reproduced this with gpg 2.0.19. It is a documented incompatability
+> between gpg 1.x and 2.x; the latter needs --batch included in its
+> parameters. I've put in a fix. [[done]]