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

Re: Relative behaviours of authz in mod_authz_svn and svnserve

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-10-10 02:49:42 CEST

David Anderson wrote:
> Say you have two repositories:
> /srv/svn/groupa/repos and /srv/svn/groupb/repos. Both are served by
> svnserve -r /srv/svn, and in both repositories, svnserve.conf lists
> "authz-db = /srv/svn/authz.conf". For both repositories, svnserve
> thinks that both are called 'repos', and thus, no possibility to discern
> between them in the authz rules.
...
> I'm not really sure how to handle this gracefully. There are two
> options as I see it:
> 1. Document the limits of authz as applied to svnserve, and hope that
> the collision situation is rare enough to not bother anyone.
>
> 2. Make mod_dav_svn and mod_authz_svn handle n-depth repositories when
> serving SVNParentPath, and make svnserve handle n-depth authz like it
> should. This makes svnserve and mod_dav_svn serve repositories equally,
> and enables both having the same authz rules and general setup if the
> repositories have to be served from both RA methods.
>
> My view is that 2. is the right thing to do, because it makes authz
> equal and uniform accross RA methods. It seems that mod_dav_svn was
> made to prevent n-depth repositories by design though. Can someone in
> the know tell me why that is? This fix would also require altering
> dav_svn_split_uri(), which likely has a lot of repercussions all over
> mod_dav_svn.
>
> Also, 2. will take more time than amending the svnbook as 1. requires.
> Is there enough time to get this fix (if it is deemed necessary and
> possible) into 1.3.0 ? The alternative, if the fix is not possible
> before 1.3.0, would be to document the lack in svnserve for 1.3.0 and
> work out a durable solution for the next release.
>
> What do people think?

I think 2. is too big for 1.3.0 at this time. Do 1. for now, and point out
the obvious workaround of simply using seperate authz-db files for the
repositories to avoid ambiguity.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 10 02:50:38 2005

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

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