diff options
| author |  jgoerzen <jgoerzen@web> | 2016-06-23 21:24:50 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-06-23 21:24:50 +0000 |
| commit | b2a29b1bf805d57db5c58547fe0bbf082c882337 (patch) | |
| tree | 1d117da7ea6110686d36eca863412628c79e0122 /doc | |
| parent | 8d0f41c875820ea3dab3d6dff0083c16e9fde6ca (diff) | |
Added a comment: A caution on this
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_4_536fbc38a7f2e7ab42188b5a8700e2cf._comment | 7 |
1 files changed, 7 insertions, 0 deletions
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 000000000..524f507e6 --- /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. +"""]] |