Re: restricting access via http.conf (was Re: svn stability problems, was: dir duplication)

solo turn wrote:
>
> we now tracked it down to apache access roles. this seems to be not
> "scale big" related.
>
> we have a role for the whole repository, and introduced a new one,
> which has only the right to work on a subtree. this made the whole
> repository behave strange:
> - checkout worked
> - commit did not
> - apache mod dav did not
> (duplicate, recursive entries)
>
> i post the details as soon i have them.
>
> i did also not yet check, if there is a known bug concerning this.
>
> is there any documentation, how to set up the security correctly for:
> - users with read/write for the whole repository
> - users with read for the whole repository
> - users with read for the whole rep, write for subtree
> - users with read for a subtree

You can use commit-access-control.pl for the first, second and third
of these. There's no easy way to prevent any user from reading any
part of the repository.

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org