[Cvsnt] Documentation on ACL features in build 43
tmh at nothing-on.tv
Sat Dec 8 11:57:15 GMT 2001
On Fri, 07 Dec 2001 20:31:27 +0000, Mike_Stopper wrote:
> It appears that Corey Minyard's site with these docs is a victim of the
> @Home debacle. Does anyone have these docs or can explain how the ACL
> mechanism in CVSNT works?
At the moment the best documentation is the cvs help system (cvs -H chacl)... I've
changed some of the semantics & added branch tags. Basically:
ACLs are per-directory. Each directory has a set of ACL lines which can
define access to a particular user/branch. There is a special entry
'default' which is used whenever there is no other applicable entry.
r - read/checkout
w - write/checkin
c - create/add (should this be changed to 'a'?)
n - no access
You need 'r' access on all parent directories before any permissions are
granted (I could possibly add another permission here for this... 'l' for
You can lock an entire branch by saying 'cvs chacl -R -r foo
default:r', then add the users who have permission to commit to it. If
you want to disable access to a branch altogether there is no need alter
the permissions of the subdirectories, so 'cvs chacl -r foo default:n' is
Users listed in the CVSROOT/admin file always have access to all
directories (again, I may change this as technically they only need the
permission to change the ACLs on all directories.... NTFS does it this
ACLs can only be changed by the directory owner (if it has one - set by
cvs chown) or an admin user.
To delete an ACL just specify no permissions for it - 'cvs chacl foo:'
This is how I expect everything to work... In the (quite likely) event it
doesn't work properly tell me what's wrong and I'll fix it for the next
Cvsnt mailing list
Cvsnt at cvsnt.org
More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter CVSNT on Facebook