[cvsnt] How to manage ACL with NTFS and SSPI ?

Gerhard Fiedler lists at connectionbrazil.com
Fri Jun 1 19:25:17 BST 2007

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.

Arthur wrote:

> My question is about CVSNT ACL : I would to control the read right on a
> file basis for a cvs repository. I use cvs chacl on sspi protocol. The
> access right works fine for the directory but do not have any effect on
> the file. 
> It's a full windows system : server and client. 
> There are 2 users : A and B. A should have access to all files. B should
> not access to *.vb files. 
> I work directly on the repository files, which have a ",v" extension. If
> I set NTFS rights so that B has not the read right on those files, when
> B tries to checkout the module, he gets an error on the RCS file.

I recommend to use CVSNT ACLs, not NTFS ACLs. Set up the repository so that
all repository users have read/write rights (possibly restrict CVSROOT to
admins, but CVSNT already handles that). Then work with (r)chacl /only/ --
no fiddling with the NTFS permissions.

In general, there is nothing that you have to do directly with the ",v"
files in the repository -- unless it's one of the very few exceptions,
you're an admin and know what you're doing. Not even normal repository
admin work requires you to work inside the repository. Work in a sandbox.


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