aboutsummaryrefslogtreecommitdiff
path: root/doc/future_proofing.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-01-08 11:48:53 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-01-08 11:48:53 -0400
commitdc70490577892424bffe1f87b73a54adff6fb988 (patch)
tree9fdfa0239a2c9c121f35f9e91ad2588d824d4d79 /doc/future_proofing.mdwn
parent7fa6c4169d762cb672a3365b146914de44a53a54 (diff)
link to new tip about encryption
Diffstat (limited to 'doc/future_proofing.mdwn')
-rw-r--r--doc/future_proofing.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/future_proofing.mdwn b/doc/future_proofing.mdwn
index c9d1f068c..e5bc89829 100644
--- a/doc/future_proofing.mdwn
+++ b/doc/future_proofing.mdwn
@@ -36,3 +36,10 @@ problem:
files end up in `lost+found`, they can easily be lifted back out into
another clone of the repository. Even if the filenames are lost,
it's possible to [[tips/recover_data_from_lost+found]].
+
+* What about encrypted special remotes? A
+ [[fairly simple shell script using standard tools|Decrypting_files_in_special_remotes_without_git-annex]]
+ (gpg and openssl) can decrypt files stored on such
+ a remote, as long as you have access to the encryption keys (which
+ are stored in the git-annex branch of the repository, sometimes
+ encrypted with your gpg key).