diff options
| author |  gernot <gernot@web> | 2014-08-01 17:57:44 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-08-01 17:57:44 +0000 |
| commit | 0c47f8a67f425f76591e42e519c63d3357d7fe5e (patch) | |
| tree | 7109b92e091104277b42da5657f12ba30efcf226 /doc/todo | |
| parent | 70769e5d09a5720c327b3e505b52ec71217b83eb (diff) | |
Diffstat (limited to 'doc/todo')
| -rw-r--r-- | doc/todo/wishlist:_Parity_files_for_encrypted_remotes.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
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 000000000..34f06ad63 --- /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? |