From 6b963426a0239f634295edc2f635e19e0639200c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 8 Jan 2016 11:48:53 -0400 Subject: [PATCH] link to new tip about encryption --- doc/future_proofing.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/future_proofing.mdwn b/doc/future_proofing.mdwn index c9d1f068cc..e5bc89829c 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).