[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Alternatives for remote access?

From: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: 2002-08-30 07:18:25 CEST

On Thu, Aug 29, 2002 at 11:59:48PM -0500, David Summers wrote:
> With SSH port-forwarding, how is CVS via ssh port-forwarding significantly
> different from Subversion via ssh port-forwarding? It seems to me that
> they both do the same thing.

Indeed, I'm shocked no one mentioned port forwarding yet. (My brain
is preoccupied by other issues, so I didn't even remember it.) Note
CVS just uses a pipe rather than a true port forward, but you could
use CVS with port forwarding if you wanted to - I have before.

1) Run the http server on an unpriviliged port but blocked via
   firewall. (Configure apache to only allow from if
   you don't trust your firewall.)
2) Have developers connect via ssh to the server.
3) Setup a local port forward to the remote machine's http server and
   access the repository locally.

ssh -L 8888: authorized-user@ssh-only-server
svn co http://localhost:8888/

There's no reason that wouldn't work. You just need to log in first
with the port forwarding options so you can do your online ops.
(I believe putty on Win32 does port forwarding, but I'm not sure.)

This is exactly why no one has really had the impetus to finish
ra_pipe - it just isn't needed. A little creativity is all that
is required. Note that you can still mount the repos via WebDAV if
you wanted to.

Awesome catch! -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 30 07:19:11 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.