subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: On commit attempt, Server sent unexpected return value (403 Forbidden) in response to CHECKOUT
Date Mon, 03 Jan 2011 19:18:29 GMT
a post-commit hook or a crontab coils update the file to keep the security
on newly created branches (top post a result of this stupid phone... sorry)

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 3 Jan 2011 15:18, "Mark Phippard" <markphip@gmail.com> wrote:
> On Mon, Jan 3, 2011 at 10:13 AM, <Benjamin.Ortega@wellsfargo.com> wrote:
>> Wow...for some reason I was under the impression that file level
restrictions didn't work...I really don't know why, but there it is.
>>
>> I don't suppose there's a way to use wild cards in the path as well?
>
> Wild-cards are not supported in authz.
>
> If you only needed this to protect writes, then you can do it with a
> pre-commit hook. The SVN repository contains svnperms.py which can do
> this:
>
> http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/
>
> However, if you need to protect read access, you cannot do it via a
> hook and the Subversion authz module does not support wildcards.
>
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/

Mime
View raw message