Re: ra_svn tunneling URL syntax

At 11:49 AM 12/4/2002, Greg Hudson wrote:

>ra_svn tunneled over ssh is a fundamentally different protocol than
>ra_svn over TCP. The URL identifies the protocol as well as the
>hostname and path. HTTP proxies are mostly transparent (you use the
>same protocol with a different endpoint), but this is not.

I'm confused. So what else is new? :-)

I'm sure you've forgotten more about ssh than I will ever know, but isn't
the protocol, once it comes out the other end of the tunnel, identical to
what goes in rather than fundamentally different?

Say I am working from home and want to use Subversion to check out code
from my work server through an ssh tunnel. I type in my trusty command line:

     ssh -l mysshid -L 60662:svn.internal.work.net:51662 ssh.public.work.net

and enter my ssh password to authenticate myself.

Now I can use "svn://localhost:60662/trunk" as the URL that I pass to the
svn client and check out from svn.internal.work.net port 51662, can't I?
And from the ra_svn protocol's point of view it is as if neither client nor
server were operating over ssh. This is transparent in the same way that
the HTTP proxy is, just different endpoints. Selecting whether to use ssh
tunneling or not is still controlled through the URL, but by the hostname
and port number combination rather than a new field in the URL. And I'm
still authenticated.

What am I missing that makes this invalid? Authorization?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 5 02:23:47 2002