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

Re: Subversion AuthZ Wildcards

From: Doug Robinson <doug.robinson_at_wandisco.com>
Date: Thu, 1 Jun 2017 18:11:39 -0400


[sorry for the delay]

On Thu, May 18, 2017 at 9:38 AM, Stefan Fuhrmann <stefan2_at_apache.org> wrote:

> On 27.02.2017 17:05, Julian Foad wrote:
>> Doug Robinson wrote:
>>> Folks:
>>> "Julian said Stefan said this could be useful." :-)
>>> I really hope it is. Best wishes and thank you all!
>> Thank you very much, Doug!
> Same here. Sadly, my talk wasn't admitted at ApacheCON
> (it seems very few were outside big data).

That's "unfortunate" - sorry.

> Doug, are we allowed to put that presentation into our Wiki?
> IMO, it covers the usual dos and donts very well.

Yes, I did the work necessary to enable you to put the work up on your
wiki. Credit to WANdisco/me.

> Also, is there some experience with strategies / suggestions
> like "put generic access first" and "put generic restrictions last"?

I've been meaning to write up some guidance. I'll try to find some time.

> Svn devs: the attachment is a presentation Doug had prepared for
>> explaining the Authz wilcard rules as implemented for WANdisco a couple of
>> years ago, which they have been using with svn 1.9.x, and which is a little
>> different from the 'authzperf' version that we have recently merged to
>> trunk for 1.10.
> The behavior in /trunk is almost identical to WD-code.
> There are two main differences:
> * /trunk now uses are specialized parser for authz.
> Some accidental features of the previously used
> config parser are no longer available. In particular,
> sections may no longer be repeated and there is
> no support for value expansion.

Just checking: can there be 2 sections of:

     * = r

     accountA = rw
     accountB = rw

Or is this now going to fail?

Can you say more about the "value expansion"?

> * An edge-case or two has been fixed concerning
> recursive access rights. Those are checked by new
> authz tests introduced in r1774890 and r1764337.
> Some of that may already be in the WD code.

We've gotten at least one fix - definitely!

> I suggested to Stefan2 that the one thing we're missing is clear
>> documentation of the new work, and to Doug that we might benefit from using
>> the content of his presentation as a starting point to create our own docs
>> for the new work.
> Yes, a simple paragraph in the release notes will
> not do. Not sure though, when exactly I will find
> time and energy to write this.
> Doug is very keen that WD's version and our "official" version of wildcard
>> support should align in the long term, and in support of this, kindly
>> agreed to contribute this for us to use as we see fit.
> Any feedback is greatly appreciated.

Again, sorry for the delay in replying. I don't get time to peruse the Dev
list all the time.
Ping me directly if you need a reply (doug.robinson_at_wandisco.com)!



T +1 925 396 1125
*E* doug.robinson_at_wandisco.com
World Leader in Active Data Replication™
*Find out more wandisco.com <http://wandisco.com/>*
If this message was misdirected, WANdisco, Inc. and its subsidiaries, 
("WANdisco") does not waive any confidentiality or privilege. If you are 
not the intended recipient, please notify us immediately and destroy the 
message without disclosing its contents to anyone. Any distribution, use or 
copying of this email or the information it contains by other than an 
intended recipient is unauthorized. The views and opinions expressed in 
this email message are the author's own and may not reflect the views and 
opinions of WANdisco, unless the author is authorized by WANdisco to 
express such views or opinions on its behalf. All email sent to or from 
this address is subject to electronic storage and review by WANdisco. 
Although WANdisco operates anti-virus programs, it does not accept 
responsibility for any damage whatsoever caused by viruses being passed.
Received on 2017-06-02 00:11:47 CEST

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