Re: [check out|read] control access feature

[Todd Denniston]

Francisco Yuste Garcia wrote:
>     Dear CVS/SUBVERSION users & developers,
>     We provide Central CVS services for hundreds of software projects
> at CERN[1].
>
>     Some of our CVS users would like to have a way to prevent read
> access to their CVS repository by developers working on other CVS projects
> hosted in our CVS services.

If it is only devs on other projects they are having problems with, then you 
can control access (both read and write) with file system permissions.  If the 
other devs don't have read and/or execute access to the project's directories 
then they can not read the project. Unix groups are the easiest thing to 
implement to control the permissions on the directories{1}.  Using multiple 
repositories{2} makes it easier to apply the permission bits, when that kind 
of setup is available.

the cvs_acls script{3} may also be something you are looking for except I 
think it is more for commit control than read control.

>     Though most of the software projects we host are open source, still 
> we have few which contain sensitive files.
>
>     We were looking for an already implemented solution in CVS or 
> SUBVERSION for this feature. Does it exist?
>
>     Thank you very much for your attention.
>     Cordial greetings; Fran.
>
> [1] http://cern.ch/cvs

{1} http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_2.html#SEC13
{2} http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_2.html#SEC22
{3} 
http://cvs.savannah.nongnu.org/viewcvs/ccvs/contrib/cvs_acls.pl?root=cvs&view=markup
http://cvs.savannah.nongnu.org/viewcvs/ccvs/contrib/cvs_acls.html?root=cvs&view=markup

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter