[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Preventing Read Access to a File

From: Wiest, Damian
Subject: RE: Preventing Read Access to a File
Date: Wed, 8 Feb 2006 17:29:21 -0600


Why not just use the UNIX group permissions system?  One downside is that,
depending on your policy, users may have to remember to issue the newgrp(1)


> -----Original Message-----
> From: Jake Colman [mailto:address@hidden 
> Sent: Wednesday, February 08, 2006 8:26 AM
> To: address@hidden
> Subject: Preventing Read Access to a File
> Can anyone suggest a method for restricting read access by 
> specified individuals to specific modules?  Using CVS' 
> commitlog script I can restrict users from committing to 
> branches and/or modules.  But how can I prevent them from 
> even seeing it?
> I don't think CVS, itself, can solve this for me.  Am I correct?
> I've looked at the cvsacl project (a patch to CVS source code 
> to support file-based ACLs) but it appears to be dormant.  
> Also, the patch is three point releases behind the current 
> version.  Does anyone know anything about this project?  Does 
> anyone know why this patch never made it into the mainline code?
> Are any of the other CVS-compatible projects (e.g., CVSNT) an 
> option?  I need to keep the repository on Solaris so using 
> NTFS ACLs is not a solution.
> Subversion does not directly support ACLs but might be able 
> to help me via WebDav and Apache.
> Has anyone else faced this problem and found a way to solve 
> it?  We have been using CVS for this project for well over 10 
> years.  I'd love to find a way to keep using it or to, at 
> least, remain compatible with it.
> Thanks!
> ...Jake
> -- 
> Jake Colman
> Sr. Applications Developer
> Principia Partners LLC
> Harborside Financial Center
> 1001 Plaza Two
> Jersey City, NJ 07311
> (201) 209-2467
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]