Re: File level ACL

On Mar 26, 2004, at 8:49 AM, Pierre Belzile wrote:

> Thanks for the suggestions yesterday. However, no solutions were
> offered. For a recap:
>    dir1/aClass.h (should be readable to all users of the library)
>    dir1/aClass.cc (should only be visible to selected users working
> on it's library)
>
> Users of the library cannot view the source code in aClass.cc. They
> can only read aClass.h. Library developpers can r/w everything.
>
> My understanding is that access controlthrough the Apache interface
> can't cut it. mod_auth_svn uses a datafile that can contain
> directories only. My suggestion would be to add file patterns as well.
> For example, I would say "*.h" is "r" for "*".
>
> It's ironic that CVS does this. (Using proper permissions on the
> files.) I can't move to subversion until something equivalent
> (hopefully better!) exists.
>
> Cheers, Pierre
I would actually probably prefer to take it one step further and allow
wildcards in general in this list. As well as limiting file access, it
would be convenient to be able to have some permissions such as
/*/branch/ type permissions where the * would represent a project
(using the /projectA/trunk style structure).

Just a thought.

-- 
Robert M. Zigweid                           rzigweid@zigweid.net
                                             http://rzigweid.zigweid.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org