[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: Stephen C. Tweedie <sct_at_redhat.com>
Date: 2002-08-30 10:00:13 CEST


On Thu, Aug 29, 2002 at 10:18:25PM -0700, Justin Erenkrantz wrote:
> 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.

Port forwarding is still not a general solution.

I've got a properly-managed, backed up, ssh-accessible shell account
on kernel.org. I've got such accounts with a couple of ISPs. On any
of these servers, I can immediately host a bitkeeper or cvs
repository. At worst I have to copy over a local binary of the bk or
cvs server.

I cannot host a svn repository on these sites.

> 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.)

I do not have permission to run permanent background daemons on these


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 30 10:01:12 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.