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

Re: Read access control with svnserver? (or must I use apache?)

From: Oliver Pajonk <oliver.pajonk_at_gmail.com>
Date: 2005-11-28 19:52:59 CET

2005/11/28, Ryan Schmidt <subversion-2005@ryandesign.com>:
> On Nov 28, 2005, at 17:14, x nooby wrote:
> > Currently I am running a svnserver that a staff of
> > about 20 programmers use. We plan to give our clients
> > access to their source code, but not to eachother's
> > source code. I believe I have to switch our server to
> > run as an Apache module in order to have such
> > fine-grained access control. Is this true?
> >
> > I have read that some people can use hook-scripts to
> > control access, but it appears to only allow you to
> > control write access.
> >
> > Is there a way to control read access using svnserver?
> I believe you will need authz for that. For Subversion 1.2.x and
> earlier it's only available with the Apache module. If you can wait
> until Subversion 1.3.0, authz will be available with svnserve as well.

Not exactly, you can just use an Apache directive like the following:

Require user <userlist here>

directly inside your <Location> directive for your SVN repository. This will
limit *write* access to a list of users, so effectively read access is
limited to everyone who access to the repository at all.

Of course this implies that you have to use Apache with mod_dav_svn.

Oliver Pajonk
Received on Mon Nov 28 20:48:52 2005

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.