summaryrefslogtreecommitdiff
path: root/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/wishlist__58___Parity_files_for_encrypted_remotes.mdwn')
-rw-r--r--doc/todo/wishlist__58___Parity_files_for_encrypted_remotes.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes.mdwn b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes.mdwn
new file mode 100644
index 000000000..34f06ad63
--- /dev/null
+++ b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes.mdwn
@@ -0,0 +1,7 @@
+I have data that has accompanying parity files. This is supposed to add some
+security to file integrity; however, it only works as long as the files are
+available unencrypted. In case of encrypted special remotes the existing parity files
+won't be of any use if the encrypted versions of files get corrupted in the remote location.
+
+Would it be worthwhile for git-annex to generate its own
+parity files for the encrypted data in encrypted special remotes?