summaryrefslogtreecommitdiff
path: root/doc/design/assistant/encrypted_git_remotes.mdwn
blob: 63b7be67a2d33eecdc69b173315dc17c780f7ad4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Encrypted git remotes are now possible 
using [git-remote-gcrypt](https://github.com/blake2-ppc/git-remote-gcrypt).

There are at least two use cases for this in the assistant:

* Storing an encrypted git repository on a local drive.
* Or on a remote server. This could even allow using github. But more
  likely would be a shell server that has git-annex-shell on it so can
  also store file contents, and which is not trusted with unencrypted data.

git-remote-gcrypt is already usable with git-annex. What's needed is
to make sure it's installed (ie, get it packaged into distros or embedded
into git-annex), and make it easy to set up from the webapp.

Hmm, this will need gpg key creation, so would also be a good opportunity
to make the webapp allow using that for special remotes too.

One change is needed in git-annex core.. It currently does not support
storing encrypted files on git remotes, only on special remotes. Perhaps
the way to deal with this is to make it consider git-remote-grypt remotes
to be a special remote type?