mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: Hmmm, seems odd such a serious bug is allowed to linger without serious investigation

Browse source
This commit is contained in:
pot 2016-08-09 19:22:49 +00:00 • committed by admin
parent 1c86f9267c
commit 47fa34de60
1 changed files with 9 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/bugs/Packfile_does_not_match_digest__58___gcrypt_with_assistant/comment_8_39139e25175ae265a4dc15f0b6b7b618._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="pot"
subject="Hmmm, seems odd such a serious bug is allowed to linger without serious investigation"
date="2016-08-09T19:22:48Z"
content="""
Should a developer not be all over this, would seem like a very major issue with the gcrypt backend (and annex's interaction with it) that this outcome could even be possible. You can't be using an encrypted store, which becomes irrepairably corrupted and with some of your data sat outside, unencrypted!
Any thoughts from more knowledgeable developers on how to fix, investigate further, or do something useful on this front?
"""]]