[Cvsnt] Documentation on ACL features in build 43

Mike_Stopper at amsinc.com Mike_Stopper at amsinc.com
Mon Dec 10 15:26:10 GMT 2001


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


--





What is the format of the CVSROOT/admin file??  Couldn't find any mention of it
in the Cederqvist docs, and just putting in the user name doesn't seem to be the
right setup, since after running

        cvs chacl -R default:r

I get this output:

cvs edit: cannot read owner file in e:/cvs/webroot: Permission denied
cvs edit: cannot open e:/cvs/webroot/perms: Permission denied
cvs edit: cannot read owner file in e:/cvs/webroot: Permission denied
cvs edit: cannot open e:/cvs/webroot/perms: Permission denied
cvs [edit aborted]: cannot open CVS/Notify: No such file or directory

when I try to edit any file in the webroot directory, even though I'm both the
directory's owner AND I'm listed in CVSROOT/admin and the perms file's O/S
attributes are read/write/execute for everyone.

Here's the output from lsacl....

        D:\sandbox\PDe\webroot>cvs lsacl
        Directory: .
        Owner: mstopper
          default:r


And here's the output from cvs edit on a file in that directory:

        D:\sandbox\PDe\webroot>cvs edit tree.html
        cvs edit: cannot read owner file in e:/cvs/webroot: Permission denied
        cvs edit: cannot open e:/cvs/webroot/perms: Permission denied
        cvs edit: cannot read owner file in e:/cvs/webroot: Permission denied
        cvs edit: cannot open e:/cvs/webroot/perms: Permission denied
        cvs edit: cannot read owner file in e:/cvs/webroot: Permission denied
        cvs edit: cannot open e:/cvs/webroot/perms: Permission denied
        cvs edit: cannot read owner file in e:/cvs/webroot: Permission denied
        cvs edit: cannot open e:/cvs/webroot/perms: Permission denied

Is this an issue with the admin file, or with ACL's in general??


Thanks.
-----------------------------------------------------
Michael Stopper
Senior Principal / SPS Technical Architect
American Management Systems, Inc.
4114 Legato Road
Fairfax, Virginia  22033
703.227.6646 Office
703.227.4696 FAX
mailto:Michael.Stopper at ams.com

|-------------------------+-------------------------+-------------------------|
|                         |   Tony Hoyle            |                         |
|                         |   <tmh at nothing-on.tv>   |           To:           |
|                         |                         |   cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook       |
|                         |   12/08/2001 06:56 AM   |           cc:           |
|                         |                         |   (bcc: Mike            |
|                         |                         |   Stopper/AMS/AMSINC)   |
|                         |                         |           Subject:      |
|                         |                         |   Re: [Cvsnt]           |
|                         |                         |   Documentation on ACL  |
|                         |                         |   features in build 43  |
|-------------------------+-------------------------+-------------------------|






[IMAGE]
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.

Permissions are:

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
list?).

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
enough.

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
way).

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
beta.

Tony
_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs


(Embedded image moved to file: pic29139.pcx)
--
[ pic29139.pcx of type application/octet-stream deleted ]
--

_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook