Re: 1.2 features: svn ls

Marcus Rueckert wrote:
> just because an user has access to one of my repos
> i dont want him to see all other repositories.

Hm, out of curiosity, would it be sufficient for your needs if the
user can *see* the other repositories (that they exist, including the
name of the repositories), but does not have access to browse whatever
folders the repositories contain?

I've read the manual sections on 'svnserve', and it seems it can be
accomplished like this.

For every repository you have, edit the file
/repos/<repo_name>/conf/svnserve.conf.

Add a password database file that is unique to the repository, eg.
repo_name-passwd.conf.

In this file, list all the users that should have read and/or write
access to the repository.
One user could access multiple repositories if you list him/her in
multiple configuration files.

Restricting some users to read access while giving others write access
is a bit more tricky.
I think it can be done by exposing the repository twice through
svnserve, eg. symlinking everything except the password file from one
repository folder to another.

This solution would prevent users from browsing the contents of
repositories where you don't want them, and it's compatible with the
directory browsing solution. It needs a bit of maintenance of course,
since you need to actually create user accounts for all your users
instead of just giving them a pointer to a secret repository..

Let me know what you think of it?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 9 17:46:11 2005