|
From: | Matthew Nicholson |
Subject: | Re: [Monotone-devel] encrypted netsync (was: merging in "serve raw 'automate stdio' over network") |
Date: | Sat, 17 Jan 2009 19:44:36 -0600 |
User-agent: | Mozilla-Thunderbird 2.0.0.17 (X11/20081018) |
Timothy Brownawell wrote:
I should also mention that I'm thinking we eventually want to move to SSH2 for encryption/authentication (pending finding a good server-side SSH2 library, there only seem to be client-only libraries available now). This would let us only need to listen in one place for both netsync and stdio (and whatever else we might come up with), and would also mean not needing to keep our own authentication code or write our own encryption code (I know I've seen requests for encrypted netsync).
Why ssh2 and not ssl/tls encryption? Just curious. I imagine ssl libraries would be more prevalent. And instead of relying on SSH for authentication, we could add the option of using PAM for authentication which is what SSH uses anyway.
-- Matthew Nicholson matt-land.com
[Prev in Thread] | Current Thread | [Next in Thread] |