summaryrefslogtreecommitdiff
path: root/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment')
-rw-r--r--doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment b/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment
index f345e64b7..9c20baad7 100644
--- a/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment
+++ b/doc/devblog/day_387__release_day/comment_1_3e48e930616917f6db1fc351d0f7e6df._comment
@@ -4,7 +4,7 @@
subject="comment 1"
date="2016-04-29T10:26:22Z"
content="""
-> A bug made encrypted special remotes that are configured to use chunks accidentially expose the checksums of content that is uploaded to the remote. Such information is supposed to be hidden from the remote's view by the encryption.
+> A bug made encrypted special remotes that are configured to use chunks accidentally expose the checksums of content that is uploaded to the remote. Such information is supposed to be hidden from the remote's view by the encryption.
What should the users do to repair this situation? How can the exposed checksums be removed from the remote? Is a `git annex sync` enough?