Re: svnserve -r not working?

Dimitri Papadopoulos-Orfanos wrote:
> Another reason was that I'd rather not give shell access to all
> Subversion users.

As I believe I noted in the message you replied to, there are some changes in
the trunk which will make this better someday. In essence, the changes permit
all svn+ssh:// access via a single user account, but in a way that maintains the
AUTHOR field (you can do it now but all commits would be from the same user).

>
> 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?

If you don't mind setting them up as individual users, you can actually force
the ssh connection to execute an application when connecting (it's part of the
authorized_keys stanza). It's actually part of how the patch I mention above
works. See this thread for:

        http://www.contactor.se/~dast/svn/archive-2004-02/0220.shtml

especially the first message cited above which shows the use of 'command=' in
the authorized_keys file.

HTH

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org