From 535ad3ba7582178c45cc23b79b07689e2e09b3f8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 26 Feb 2020 18:30:20 -0400 Subject: [PATCH] comment --- ..._cc348093cb5c7626930542379a82a729._comment | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 doc/bugs/gcrypt_special_remote_not_working/comment_3_cc348093cb5c7626930542379a82a729._comment diff --git a/doc/bugs/gcrypt_special_remote_not_working/comment_3_cc348093cb5c7626930542379a82a729._comment b/doc/bugs/gcrypt_special_remote_not_working/comment_3_cc348093cb5c7626930542379a82a729._comment new file mode 100644 index 0000000000..5b39a6eabe --- /dev/null +++ b/doc/bugs/gcrypt_special_remote_not_working/comment_3_cc348093cb5c7626930542379a82a729._comment @@ -0,0 +1,35 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2020-02-26T22:22:38Z" + content=""" +I'm releasing a fix now. + +It didn't seem practical to make git-annex automatically clean up any +encrypted data that got stored by mistake. For one thing, this leakage may +have consequences that git-annex users will need to work through on their +own. (sigh) Also, I just didn't see a good way to make it automatically +delete it. + +So, the release announcement just has this advice for how to recover: + + If your remotes are affected, you will want to make sure to delete + any content that git-annex has stored on them that is not encrypted! + + One way to do so is, before upgrading to this version, + run git-annex move --from the affected remotes. It will move + only the content that was not encrypted. + +I think that will be sufficient for most. It's also possible +that some may need to run `git annex fsck --fast --from` on affected +remotes, if git-annex got confused about encrypted content that was stored +on them not being present, because it wrongly was looking for non-encrypted +content. I think that would only be necessary if a similar fsck was +run earlier using the broken git-annex version. + +If you have encountered this problem and need help with recovery, post +a comment. + +Very sorry about this mess. [[todo/network_test_suite]] is needed to +be sure such problems are caught. +"""]]