link to new tip about encryption
This commit is contained in:
parent
498bd6fb43
commit
6b963426a0
1 changed files with 7 additions and 0 deletions
|
@ -36,3 +36,10 @@ problem:
|
||||||
files end up in `lost+found`, they can easily be lifted back out into
|
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,
|
another clone of the repository. Even if the filenames are lost,
|
||||||
it's possible to [[tips/recover_data_from_lost+found]].
|
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).
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue