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

Re: SVN+SSH access not advisable

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 25 Jul 2008 16:47:56 +0200

On Fri, Jul 25, 2008 at 09:41:48AM -0500, Michael L Brown wrote:
> We use svn+rsh (in the building) and svn+ssh for those who work in the
> building and remotely.
> If someone was able to get a shell, so what. Why? Because they have an
> account and a login on the system anyway, so if they want a shell, they
> can get one by either doing rsh or ssh to any system on the internal LAN.
> The ssh login to SVN is not a SVN only use login.
> Using svn+rsh/svn+ssh has never given us any trouble.
> YMMV :-)

Yes, it depends. Where I employed ssh key restriction, we could
not easily run apache+https on the server, so we were forced to
use svn+ssh to get any form of encryption. That did not mean
that we wanted to give committers shells on the server though!


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-25 16:49:46 CEST

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

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