[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [check out|read] control access feature

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-02-09 14:04:09 CET

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
Received on Thu Feb 9 15:28:59 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.