Re: commit-access-control vs. AuthzSVNAccessFile

Lukas Ruf wrote:

> - AuthzSVNAccessFile sections:
> Am I right that the sections support perl-regex as well?
> i.e.:
>
> [repos:/[a-e]]
> * =
>
> [repos:/[f-i]]
> * = r
>
> [repos:/[j-z]]
> * = rw
>

No, you cannot put any regexps or pattern-matching expressions into the
square-bracket sections.

> - Is there any fundamental difference from a user perspective between
> AuthzSVNAccessFile and commit-access-control except that
> AuthzSVNAccessFile is more powerful by that it allows also to deny
> access to a project completely?

Correct. The user doesn't know which authz system the server is using.
  (By the way, the third choice is svnperms.py.)

>
> - Am I right that I do not need to restart apache2 every time I
> modified anything in an access control file of AuthzSVNAccessFile?
>

Correct.

> - Parent directories must be accessible if a directory must be
> accessed?
> i.e.:
> [repos:/[a-e]]
> * = r
>
> [repos:/[a-e]/input]
> * = rw
>
> would work
>
> while
>
> [repos:/[a-e]]
> * =
>
> [repos:/[a-e]/input]
> * = rw
>
> wouldn't?

No, the second one would work as well. The rules "stack" from highest
level to lowest level, overriding each other as more fine-tuned
exceptions. In your second example, nobody can access /apple, but
there's a second rule which overrides the first rule for the path
/apple/input, which everyone can access.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 19 15:31:56 2004