[Top][All Lists]

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

Re: [check out|read] control access feature

From: Todd Denniston
Subject: Re: [check out|read] control access feature
Date: Thu, 09 Feb 2006 09:10:57 -0500
User-agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)

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.



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

reply via email to

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