From 5403818b47a636a73cb5c49ffd882675620e14b8 Mon Sep 17 00:00:00 2001 From: jgoerzen Date: Thu, 23 Jun 2016 21:24:50 +0000 Subject: [PATCH] Added a comment: A caution on this --- .../comment_4_536fbc38a7f2e7ab42188b5a8700e2cf._comment | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_4_536fbc38a7f2e7ab42188b5a8700e2cf._comment diff --git a/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_4_536fbc38a7f2e7ab42188b5a8700e2cf._comment b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_4_536fbc38a7f2e7ab42188b5a8700e2cf._comment new file mode 100644 index 0000000000..524f507e62 --- /dev/null +++ b/doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_4_536fbc38a7f2e7ab42188b5a8700e2cf._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="jgoerzen" + subject="A caution on this" + date="2016-06-23T21:24:49Z" + content=""" +Although I believe Joey's analysis is correct, I want to interject a caution: while investigating this issue on my own system, I discovered that a gcrypt remote has an unencrypted pack file and unencrypted index, which somehow contained actual data of mine. I would consider it a git-annex bug that data (file contents) wound up in a pack file (this is a git-annex assistant repo) but a gcrypt bug that it made it there unencrypted. +"""]]