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

svn 1.10: mod_authz no longer combines ACL entries

From: Michael Ruder <rudermi_at_gmx.de>
Date: Wed, 4 Jul 2018 13:25:19 +0200


we used up to and including svn 1.9 an authz file of the format

company = user1, user2, user3
customer = customer1, customer2

# company can read-write on everything
@company = rw

@customer = r


This gave company full rights on both project1 and project2 and customer
reading rights on project1. Now, with svn 1.10, company cannot access
anything (customer can still read project 1). So apparently, only the ACLs
in the most specific matching block are used and parent ACLs not at all.

Even like this, within a single repository, this is the case:

@company = rw

@customer = r

It results, that in trunk/src and below ONLY customer can read, company
has no rights.

Is this really an intentional change? It results in our case in a huge
amount of duplicated ACL entries and seems a rather drastic change
regarding backwards compatibility.

Best regards,

.      -Michael
Received on 2018-07-04 13:27:36 CEST

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.