diff options
author | Joey Hess <joey@kitenet.net> | 2013-09-27 16:36:58 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2013-09-27 16:36:58 -0400 |
commit | c3834ceace891ae0c0493b9d03d04484ff106b42 (patch) | |
tree | 92b7c90f2004fff41890e97b75db1f001821527d /doc | |
parent | 82b10105c4648868967550e363b73d5cdcd9f8de (diff) |
devblog
Diffstat (limited to 'doc')
-rw-r--r-- | doc/devblog/day_23__GNU_day.mdwn | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/devblog/day_23__GNU_day.mdwn b/doc/devblog/day_23__GNU_day.mdwn new file mode 100644 index 000000000..4ce90aa60 --- /dev/null +++ b/doc/devblog/day_23__GNU_day.mdwn @@ -0,0 +1,23 @@ +Worked on making the assistant able to merge in existing encrypted +git repositories from rsync.net. + +This had two parts. First, making the webapp UI where you click to enable a +known special remote work with these encrypted repos. Secondly, handling +the case where a user knows they have an encrypted repository on rsync.net, +so enters in its hostname and path, but git-annex doesn't know about that +special remote. The second case is important, for example, when the +encrypted repository is a backup and you're restoring from it. It wouldn't +do for the assistant, in that case, to make a *new* encrypted repo and +push it over top of your backup! + +Handling that neat trick. It has to do quite a lot of probing, including +downloading the whole encrypted git repo so it can decrypt it and merge it, +to find out about the special remote configuration used for it. This all +works with just 2 ssh connections, and only 1 ssh password prompt max. + +Next, on to generalizing this rsync.net specific code to work with +arbitrary ssh servers! + +---- + +Today's work was made possible by [RMS's vision 30 years ago](http://article.olduse.net/771@mit-eddie.UUCP). |