You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Steven Op de beeck <an...@ulyssis.org> on 2003/11/02 11:56:36 UTC
problems tunneling svn+ssh
Hi,
I'm having some problems tunneling svn+ssh.
From "http://subversion.tigris.org/project_faq.html#paranoid"
I got this:
% ssh -L 8888:svn-server.example.com:80 me@ssh-server.example.com
% svn checkout http://localhost:8888/repos/ours
So I thought this would work for svn+ssh too.
Here's a drawing of the situation.
____________> PORT_FORWARD >___________
| |
| |
SOMEWHERE <---------> MERCURY <-------||NAT+FIREWALL|------> FURY
svn client (external) (internal)
ssh-daemon
svn server
On FURY:
$ ssh -R 2223:localhost:22 -l steven MERCURY -gN
On SOMEWHERE:
$ssh -p 2223 MERCURY
This works perfectly, so the ssh-tunnel is functioning.
Then, still on SOMEWHERE:
$ svn co svn+ssh://mercury:2223/usr/local/repos/mume
The authenticity of host 'mercury (x.x.x.x)' can't be established.
RSA key fingerprint is 73:37:11:6c:a7:2f:23:12:08:e6:c1:ad:9f:ba:11:89.
[...]
bash: line 1: svnserve: command not found
svn: Network connection closed unexpectedly
svn: Connection closed unexpectedly
After deleting the key from known_hosts:
$ ssh MERCURY
RSA key fingerprint is 73:37:11:6c:a7:2f:23:12:08:e6:c1:ad:9f:ba:11:89.
You can see the RSA fingerprints are the same, so it seems to me that
"svn+ssh://mercury:2223/usr/local/repos/mume" doesn't use the 2223 port
(but the default 22)
To confirm this, the remote host, FURY, has this fingerprint:
$ ssh -p 2223 404.be
[...]
RSA key fingerprint is 79:f8:47:c7:00:96:f0:dd:0e:a8:fa:f5:40:d5:54:47.
------------
To conclude,
Unlike the http example above, svn doesn't seem to use the specified
port in svn+ssh://mercury:2223/usr/local/repos/mume
Is this a bug? Or wasn't it intended to be used like this?
I hope my problem is clear, does anyone know a solution?
tia,
Steven.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: problems tunneling svn+ssh
Posted by Anthony Baxter <an...@interlink.com.au>.
>>> Garrett Rooney wrote
> Subversion doesn't know how to tell every ssh client in the world how
> to use a non-default port. To work around that fact, you can set the
> SVN_SSH environment variable to 'ssh -p 2223' or whatever your
> particular ssh client requires, or add a similar setting to your config
> files.
Note that if you also want to access the host on the normal port, you
can do something like
Host svnhostname
Hostname real.host.name
Port 2223
in the config file...
--
Anthony Baxter <an...@interlink.com.au>
It's never too late to have a happy childhood.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: problems tunneling svn+ssh
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
>
> To conclude,
> Unlike the http example above, svn doesn't seem to use the specified
> port in svn+ssh://mercury:2223/usr/local/repos/mume
> Is this a bug? Or wasn't it intended to be used like this?
Subversion doesn't know how to tell every ssh client in the world how
to use a non-default port. To work around that fact, you can set the
SVN_SSH environment variable to 'ssh -p 2223' or whatever your
particular ssh client requires, or add a similar setting to your config
files.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org