2013-04-02 21:14:58 +00:00
|
|
|
Encrypted git remotes are now possible
|
2013-11-07 16:29:13 +00:00
|
|
|
using [git-remote-gcrypt](https://github.com/joeyh/git-remote-gcrypt).
|
2013-04-02 21:14:58 +00:00
|
|
|
|
|
|
|
|
There are at least two use cases for this in the assistant:
|
|
|
|
|
|
2013-10-01 23:12:08 +00:00
|
|
|
* Storing an encrypted git repository on a local drive. **done**
|
2013-04-02 21:14:58 +00:00
|
|
|
* 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.
|
2013-10-01 23:12:08 +00:00
|
|
|
**done**
|
2013-04-02 21:14:58 +00:00
|
|
|
|
|
|
|
|
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
|
2013-10-01 23:12:08 +00:00
|
|
|
into git-annex), and make it easy to set up from the webapp. **done**
|
2013-04-02 21:14:58 +00:00
|
|
|
|
|
|
|
|
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
|
2013-10-01 23:12:08 +00:00
|
|
|
to be a special remote type? **done**
|
