You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Francisco Yuste Garcia <fr...@cern.ch> on 2006/02/09 11:15:43 UTC
[check out|read] control access feature
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.
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
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Francisco Yuste Garcia mailto:francisco.yuste.garcia@cern.ch
CERN Dept. IT/DES Phone : +41 22 767 95 38
Blg. 31-3-031 CH-1211 Geneva 23, Switzerland
System Infrastructure Services
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: [check out|read] control access feature
Posted by Kevin Greiner <gr...@gmail.com>.
On 2/9/06, Francisco Yuste Garcia <fr...@cern.ch> wrote:
>
> 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.
http://subversion.tigris.org/svn_1.3_releasenotes.html#svnserve-authz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: [check out|read] control access feature
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 9, 2006, at 12:15, 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.
>
> 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?
Subversion can handle this, no problem. If all your projects are in a
single repository, then you can use authz to limit users' access to
specific paths within the repository as you see fit. If each project
is its own repository, then that's even easier. authz used to be
available through the Apache2 server only, but as of Subversion 1.3.0
it is available in the svnserve server as well. You can read about
all of this in the Subversion book at http://svnbook.org .
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org