diff options
author | Joey Hess <joey@kitenet.net> | 2013-09-26 18:48:32 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2013-09-26 18:48:32 -0400 |
commit | 08bbd0f277f6ed1b4fe3a2ed6fa6ae1e04c6374d (patch) | |
tree | 25dd18229c85ec1fc10a528f06a0fd7492e266cb | |
parent | e30d4f646e73a3113d6cab4fab9c4434ea16a9e0 (diff) |
devblog
-rw-r--r-- | doc/devblog/day_22__gcrypt_on_rsync.net.mdwn | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/devblog/day_22__gcrypt_on_rsync.net.mdwn b/doc/devblog/day_22__gcrypt_on_rsync.net.mdwn new file mode 100644 index 000000000..b827efc13 --- /dev/null +++ b/doc/devblog/day_22__gcrypt_on_rsync.net.mdwn @@ -0,0 +1,20 @@ +Being still a little unsure of the UI and complexity +for configuring gcrypt on ssh servers, I thought I'd start today with the +special case of gcrypt on rsync.net. Since rsync.net allows running some git +commands, gcrypt can be used to make encrypted git repositories on it. + +Here's the UI I came up with. It's complicated a bit by needing to explain +the tradeoffs between the rsync and gcrypt special remotes. + +[[!img /assistant/rsync.net.encryption.png]] + +This works fine, but I did not get a chance to add support for enabling +existing gcrypt repos on rsync.net. Anyway, most of the changes to make +this work will also make it easier to add general support for gcrypt on ssh +servers. + +Also spent a while fixing a bug in git-remote-gcrypt. Oddly +`gpg --list-keys --fast-list --fingerprint` does not show the fingerprints +of some keys. + +Today's work was sponsored by Thomas Djärv. |