diff options
-rw-r--r-- | doc/design/assistant.mdwn | 2 | ||||
-rw-r--r-- | doc/design/assistant/encrypted_git_remotes.mdwn | 21 |
2 files changed, 22 insertions, 1 deletions
diff --git a/doc/design/assistant.mdwn b/doc/design/assistant.mdwn index e35338708..a6e834409 100644 --- a/doc/design/assistant.mdwn +++ b/doc/design/assistant.mdwn @@ -31,7 +31,7 @@ We are, approximately, here: * [[rate_limiting]] * [[partial_content]] -* encrypted git remotes using [git-remote-gcrypt](https://github.com/blake2-ppc/git-remote-gcrypt) +* [[encrypted_git_remotes]] * [[deltas]] * [[leftovers]] * [[other todo items|todo]] diff --git a/doc/design/assistant/encrypted_git_remotes.mdwn b/doc/design/assistant/encrypted_git_remotes.mdwn new file mode 100644 index 000000000..63b7be67a --- /dev/null +++ b/doc/design/assistant/encrypted_git_remotes.mdwn @@ -0,0 +1,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? |