summaryrefslogtreecommitdiff
path: root/doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files
diff options
context:
space:
mode:
authorGravatar interfect@b151490178830f44348aa57b77ad58c7d18e8fe7 <interfect@web>2017-06-09 01:48:15 +0000
committerGravatar admin <admin@branchable.com>2017-06-09 01:48:15 +0000
commit597eee71e0424d63f14a105f9d8c16837dcee20d (patch)
treeefa94497a57d066ae0a4fd2dcb3204b63c7b6586 /doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files
parentb3835c63c8a9aaf30fa87b7e9adb8664d7da313a (diff)
Added a comment
Diffstat (limited to 'doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files')
-rw-r--r--doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files/comment_4_81abd2627672911ba6367effbf5c487b._comment9
1 files changed, 9 insertions, 0 deletions
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.
+"""]]