diff options
| author |  dusty@dba9614abc02e013134f95c2c59181a6c12a8468 <dusty@web> | 2015-07-27 04:41:43 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-07-27 04:41:43 +0000 |
| commit | 04680f1b75338926731e6df27fc702bd73f07a6c (patch) | |
| tree | c8ca269daff9582bddd2774fba960cd9ab0e2215 | |
| parent | 60941e096483870c3e3fbd0319d48b812fcd8e90 (diff) | |
| -rw-r--r-- | doc/forum/Full_restore_from_an_encrypted_special_remote.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/Full_restore_from_an_encrypted_special_remote.mdwn b/doc/forum/Full_restore_from_an_encrypted_special_remote.mdwn new file mode 100644 index 000000000..d724929b0 --- /dev/null +++ b/doc/forum/Full_restore_from_an_encrypted_special_remote.mdwn @@ -0,0 +1,3 @@ +If I lose all my git-annex repositories is it possible to restore the content of a repo from a special remote in which encryption was enabled? I know git-annex isn't designed to be a backup solution but more for the archive and/or nomad use case. I do like the idea of being able to restore the files from an S3 special remote though. I imagine part of the answer to this question has to do with what type of encryption is used (hybrid and shared key rely on information stored in the repo but pubkey doesn't rely on the repo at all) and would probably be easier if there were an option to disable hashing the filenames of the files (less secure, but maybe ok in some cases). + +Thoughts? |