diff options
author | 2016-04-14 16:08:35 -0400 | |
---|---|---|
committer | 2016-04-14 16:08:35 -0400 | |
commit | ee81a22b29263a53e6f374a362f8ff7355b29665 (patch) | |
tree | 243f4da5c51c740b994f1a8682cb14a569f2a1c8 | |
parent | 448a1720a3f5322f4bcc50e11461d7ae3cfbe730 (diff) |
comment
-rw-r--r-- | doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_3_2432df64f920f3962b6ba02adaa9b61d._comment | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_3_2432df64f920f3962b6ba02adaa9b61d._comment b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_3_2432df64f920f3962b6ba02adaa9b61d._comment new file mode 100644 index 000000000..bfdddc9c7 --- /dev/null +++ b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_3_2432df64f920f3962b6ba02adaa9b61d._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-04-14T19:57:58Z" + content=""" +Ok, so definitely not a bug in git-annex then. + +`get_verify_decrypt_pack` downloads an encrypted pack file, and then +uses gpg to hash the pack file and compares this to the hash +encoded in the name of the pack file. + +So, this could happen if the pack files in the gcrypt remote have gotten +the wrong data into them. Or it could be a bug of some kind in +git-remote-gcrypt. +"""]] |