summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-07-14 20:54:32 +0000
committerGravatar admin <admin@branchable.com>2014-07-14 20:54:32 +0000
commit74ae7ae611c71ea0f4f0b96e6ac30607de45651c (patch)
treec12203a3e443eab62c116b6de300531ef57558b3
parentba9000ce31ec20ae496ec76b972d93294f623d6b (diff)
Added a comment
-rw-r--r--doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment
new file mode 100644
index 000000000..01b9726a9
--- /dev/null
+++ b/doc/bugs/using_gpg_encryption_with_multiple_keys_fails/comment_1_584390159278577da78b05bc7bb0e673._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.2"
+ subject="comment 1"
+ date="2014-07-14T20:54:32Z"
+ content="""
+AFAICs, this is a known bug in git-remote-gcrypt: <https://github.com/blake2-ppc/git-remote-gcrypt/issues/9>
+
+In your log, it encrypts to A1FE7E9BECB5C7CA. I think this is the new key that git-annex generated. The problem comes when trying to decrypt the manifest, then it tries every gpg key until it finds one that works.
+"""]]