On Oct 22, 2004, at 1:54 PM, Erik Huelsmann wrote:
> On Fri, 22 Oct 2004 13:37:46 -0400, Scott Palmer
> <scott.palmer@2connected.org> wrote:
>>>
>>> It does :-)
>>>
>>> The authorisation takes place at the repository hook level - so it
>>> works
>>> just as well with any access method.
>>>
>>
>> I was under the impression that using svn: the only security was
>> read-only vs. read-write for the whole repository, and that you could
>> not apply different security based on the path. So with svn: the
>> 'tags' folder can't be made read-only independently of the trunk and
>> other 'copies'.
>>
>> From the Subversion book:
>> "Notice that svnserve only understands "blanket" access control. A
>> user either has universal read/write access, universal read access,
>> or
>> no access."
>
> Right, it comes out of the box that way, but you can limit it further
> with hook-scripts.
>
>> So I think my claim still stands.
>
> Not really, we gave you the most general mechanism you can wish to do
> your own authorisation: your own creativity :-)
>
>> Note that pre-commit hooks to support this are not provided. If I have
>> to do my own hook programming it is basically to work around the lack
>> of the true feature. Otherwise I would just enable the "feature".
>
> Umm, yes, they are. See the svnperms.py script in
> http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ it controls
> add, update and remove. which means that you can make tags/
> add-but-never-change. No programming, just a conf file.
Ok, that is better than what I thought I would have to deal with. It
should be mentioned at the same place in the Subversion book that I
quoted. And whoever maintains the pre-built packages and Windows
installer should consider including these things. Where are the docs
for this hook script?
There are still some negative things... it requires yet another third
party extension, since I run on Windows which does not come with
Python... but I can live with installing that.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 22 21:26:30 2004