svnserve/ssh tunnel?

[Jonathan Blow <jo...@number-none.com>]

Hi, I am trying out subveresion but I don't want to deal with the pain of
apache, so I am trying to use svnserve.  I have a linux server and a win32
client.  From the win32 client, I keep an ssh tunnel to the
server for various purposes (mail, etc) and I have added a port for
subversion.

In the install.txt and the Subversion book, it mentions there's a [tunnels]
section in the servers file where I can specify the value of 'ssh'.  So,
anyway, I try to add that:

    [tunnels]
    ssh = telnet localhost 3690

But actually, no matter what I try to set the value of 'ssh' to, it just
doesn't make a difference, the behavior of the svn client is always
the same.  When I try to do this:

    svn co svn+ssh://localhost/home/svn/code

it just hangs until I ctrl-c it.  I assume I am doing something subtly
wrong, but what that is is just not evident.  Before anyone asks,
the ssh tunnel is definitely working; I can telnet localhost 3690 from 
the command line on the win32 machine and see the 
LISP-looking svn protocol greet me.

This is with svn 0.26.0, by the way.  Any help would be appreciated,
thanks.

  -J.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svnserve/ssh tunnel?

[Jan Braun <ja...@gmx.de>]

Jonathan Blow wrote:
> 
> the ssh tunnel is definitely working; I can telnet localhost 3690 from
> the command line on the win32 machine and see the
> LISP-looking svn protocol greet me.

Then you should use

    svn co svn://localhost/home/svn/code

since you have the subversion server already listening on port 3690 of
localhost (via the ssh tunnel, but the client won't know the
difference to a locally running svnserve).
As Ben points out, svn+ssh is for telling the client (how) to create a
tunnel on it's own.
I hope that helps to clarify.

	Jan


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svnserve/ssh tunnel?

[Ben Collins-Sussman <su...@collab.net>]

"Jonathan Blow" <jo...@number-none.com> writes:

>     [tunnels]
>     ssh = telnet localhost 3690
> 
> But actually, no matter what I try to set the value of 'ssh' to, it just
> doesn't make a difference, the behavior of the svn client is always
> the same.  When I try to do this:
> 
>     svn co svn+ssh://localhost/home/svn/code
> 
> it just hangs until I ctrl-c it.  I assume I am doing something subtly
> wrong, but what that is is just not evident.  Before anyone asks,
> the ssh tunnel is definitely working; I can telnet localhost 3690 from 
> the command line on the win32 machine and see the 
> LISP-looking svn protocol greet me.

'telnet localhost 3690' only proves that there's an svnserve daemon
listening to that port number.  But that's not relevant to what you're
trying to do.

If you look at the subversion book (chapter 5), it explains that
svn+ssh:// is very different from svn://.  The former command uses ssh
to authenticate (on port 22) and then *launches a private svnserve
process* on the server, which communicates back through the tunnel.
The latter command just opens an unauthenticated connection directly
to port 3690.  There's no 'tunnel' going on.

'ssh' was written as replacement for 'rsh', which was designed to
launch programs on remote computers.  'telnet' will not do this.  You
need a real ssh program for win32.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org