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

Re: Restricted access by branch

From: Ximon Eighteen <ximon.eighteen_at_int.greenpeace.org>
Date: 2005-09-27 18:05:51 CEST

Jason House wrote:
> Is it possible to have multiple "branches" with shared history, but to
> restrict certain users from access to particular branches? Any guidance
> on how I could do this would be greatly appreciated.

Since branches are (if you follow the suggested structure) just
directories inside your repository you can use (if using mod_authz_svn,
or the upcoming (I think) support in svnserve for similar permission
controls) the mod_authz_svn access control file with something like:

sally = r
* =

Or whatever permission model you want.

Restricting access via other tools that talk to your repository (such as
ViewCVS) depends on how the tool works. If it talks to the repository as
any client would then its access can be controlled. If however like
ViewCVS it talks locally directly to the repository I think you need
support in ViewCVS. I have hacked (badly) my copy of ViewCVS borrowing a
little code from the Trac project and some of my own in combination with
an Apache configuration that uses mod_authz_svn to apply basic auth to
my ViewCVS URLs too (extra code for the query.py part of ViewCVS was
required, this obviously cannot use URL based protection).


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 27 18:12:29 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.