Merge branch 'master' of ssh://git-annex.branchable.com

3 files changed, 34 insertions, 0 deletions

diff --git a/doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files/comment_3_414bd487619e46b25e8d9a57d9aef1f6._comment b/doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files/comment_3_414bd487619e46b25e8d9a57d9aef1f6._comment
new file mode 100644
index 000000000..bc136ec45
--- /dev/null
+++ b/doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files/comment_3_414bd487619e46b25e8d9a57d9aef1f6._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="interfect@b151490178830f44348aa57b77ad58c7d18e8fe7"
+ nickname="interfect"
+ avatar="http://cdn.libravatar.org/avatar/3ba541a3204f4ea4b274049a152489c5"
+ subject="comment 3"
+ date="2017-06-09T01:40:00Z"
+ content="""
+Unfortunately even though the content is still over at Amazon, ACD can no longer be accessed through rclone, so I can't get Git Annex to go over there and download it.
+
+With the new chunk-supporting decryption script (which I further modified to actually use the timestamps on the log entries), I am able to generate the right key for my test file. I was also able to generate the key for and decrypt another test file, and then testing with git annex again shows that I can successfully fsck other file in the remote.
+
+I think what is happening is that my small file I was testing with somehow became corrupted or was modified while on Amazon's servers. I downloaded from Amazon before the transfer and from Google after and did a diff, and both files are identical, so I think I moved over corrupt data. 
+
+It looks like git annex is just successfully doing its job and identifying some data corruption here. The bug can probably be closed.
+
+
+"""]]
diff --git a/doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files/comment_4_81abd2627672911ba6367effbf5c487b._comment b/doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files/comment_4_81abd2627672911ba6367effbf5c487b._comment
new file mode 100644
index 000000000..66c23ee4f
--- /dev/null
+++ b/doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files/comment_4_81abd2627672911ba6367effbf5c487b._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="interfect@b151490178830f44348aa57b77ad58c7d18e8fe7"
+ nickname="interfect"
+ avatar="http://cdn.libravatar.org/avatar/3ba541a3204f4ea4b274049a152489c5"
+ subject="comment 4"
+ date="2017-06-09T01:48:15Z"
+ content="""
+I'm actually seeing a lot of files (mostly smaller ones, for some reason) failing to fsck because GPG decryption failed. I can't tell at the moment whether they got corrupted in the transfer, or corrupted in the initial upload somehow. I'm pretty sure the problem here isn't with git annex itself, or more people would have noticed, but I'm definitely going to be fscking my cloud remotes more frequently.
+"""]]
diff --git a/doc/forum/Preferred_content_settings_for_sets_of_backup_drives__63__/comment_2_c21e128f6bdd5408607b51c963854d4d._comment b/doc/forum/Preferred_content_settings_for_sets_of_backup_drives__63__/comment_2_c21e128f6bdd5408607b51c963854d4d._comment
new file mode 100644
index 000000000..d85c26609
--- /dev/null
+++ b/doc/forum/Preferred_content_settings_for_sets_of_backup_drives__63__/comment_2_c21e128f6bdd5408607b51c963854d4d._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="jeff"
+ avatar="http://cdn.libravatar.org/avatar/6f3f360b92a588e1b0999bbd4707ce12"
+ subject="comment 2"
+ date="2017-06-07T21:24:36Z"
+ content="""
+Thanks! I missed that you can put group names in the \"copies=\" part.
+"""]]