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

Re: svnserve -r not working?

From: Dimitri Papadopoulos-Orfanos <papadopo_at_shfj.cea.fr>
Date: 2004-04-28 09:54:58 CEST


> svn+ssh:// spawns a custom svnserve instance for each connection; it is
> much more closely related to using file:// from a local account. It
> doesn't attach to the svnserve instance you started above. See this for
> more details:
> http://svnbook.red-bean.com/svnbook/ch06s03.html#svn-ch-6-sect-3.3
> especially the second paragraph after the example code.

That's one of the reasons that convinced me using Apache is a better
solution than svnserve + SSH for authenticated access - although it
seems much more involved at first sight.

Another reason was that I'd rather not give shell access to all
Subversion users. With Perforce, I was able to create accounts with
/bin/false as the shell, because SSH was only used for tunnelling a
connection to the Perforce daemon already running on server. Then users
would connect using:
        ssh -N
where -N stands for:
        Do not execute a remote command. This is useful for just
        forwarding ports (protocol version 2 only).

Since in the Subversion case SSH has to spawn its own svnserve instance,
is there any other way to constrain Subversion users to run svnserve and
nothing else? I guess one should use a constrained shell, but I have no
experience with that. Does anyone have some recipe/shell/script to share?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 28 09:55:34 2004

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.