[cvsnt] Re: CVSNT not enforcing read-only ACL

Gerhard Fiedler lists at connectionbrazil.com
Sun Jul 3 18:49:39 BST 2005


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.


Marco Rinaudo wrote:

> now let check that my ACLs are set as I was expecting:
> 
> ------------------------
> [root at power test]# cvs -d :pserver:MyLogin:MyPassword at MyServer.Com:/cvs 
> lsacl mymodule
> Directory: mymodule
> Owner: MyLogin
> 
> user=myuser
>         read
> [root at power test]# cvs -d :pserver:MyLogin:MyPassword at MyServer.Com:/cvs 
> rlsacl mymodule
> Directory: mymodule
> Owner: MyLogin
> 
> user=myuser
>         read
> ----------------------------------------
> 
> I eventually managed to sucessfully set "read" rights for the user named 
> myuser under the module named mymodule.
> I am now expecting that myuser is not able to WRITE under mymodule, she is 
> supposed to be ONLY able to read not to write. Am I wrong?

I'm not sure, but I think you have to /remove/ the write permission. AFAIK
it's granted by default, so the only thing you've done with this is to add
an explicit read permission to the default read/write permission.

I guess what people do who want to have only explicit rights in their
repositories is to issue a deny everything command for everybody on the
root directory, which then makes the default to be all denied. Then you
enable explicitly the rights you want to give, on the individual modules.

Or you start out with everything granted (the default), and only deny
specific rights to specific users our groups.

Gerhard



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