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 0000000000..bfdddc9c7f
--- /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.
+"""]]