From 0b078b2d37a832c36f4988a6f56046353a7508ac Mon Sep 17 00:00:00 2001 From: gernot Date: Fri, 1 Aug 2014 17:57:44 +0000 Subject: [PATCH] --- doc/todo/wishlist:_Parity_files_for_encrypted_remotes.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/todo/wishlist:_Parity_files_for_encrypted_remotes.mdwn diff --git a/doc/todo/wishlist:_Parity_files_for_encrypted_remotes.mdwn b/doc/todo/wishlist:_Parity_files_for_encrypted_remotes.mdwn new file mode 100644 index 0000000000..34f06ad633 --- /dev/null +++ b/doc/todo/wishlist:_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?