Re: netsync over ssh revisited

In message <[email protected]> on Wed, 05 Sep 2012 08:20:58 -0400, Stephen Leake <[email protected]> said:

stephen_leake> Richard Levitte <[email protected]> writes:
stephen_leake> 
stephen_leake> > So I wonder, has anyone else already played with having netsync
stephen_leake> > tunneled over ssh but otherwise working exactly like the usual mtn:
stephen_leake> > schema?  (in other words, it still requires a mtn running as server on
stephen_leake> > the remote end)
stephen_leake> 
stephen_leake> I have not tried it, but you can probably get there with ssh port forwarding.
stephen_leake> 
stephen_leake> > My other question is, is there any reason why monotone shouldn't
stephen_leake> > support that?  A mtn+ssh: schema, say?  Technically, it shouldn't be
stephen_leake> > harder than supporting the current ssh: schema.
stephen_leake> 
stephen_leake> There was discussion of using ssl, a while back.

I had a look in std_hooks.lua and noticed the ssh+ux: schema, which
basically does what I'm after...

Actually, googling it, I was reminded of some emails around that
schema.  Unfortunately, it seems to be undocumented, something that
should be corrected.

The only real trouble with the ssh+ux: schema is that it won't work
with usher (and I really see no way to do that either, as usher relies
on the path to distinguish between servers to proxy for...  or maybe
it should make sockets out of those...  hmm...).
I'm thinking that a mtn+ssh: schema should work similarly to the
ssh+ux: schema, but instead of this:

    ssh {host} socat - UNIX-CONNECT:{path}

it would do this:

    ssh {host} socat - TCP-CONNECT:localhost:4691

Cheers,
Richard

-- 
Richard Levitte                         [email protected]
                                        http://richard.levitte.org/

"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish