> From: Glenn A. Thompson [mailto:email@example.com]
> Sent: 23 May 2002 07:57
> Greg Hudson wrote:
> > Is that "authentication" or "authorization"?
> Boy do I want to know more about this.
> After reading the design document some time ago, I assumed that
Ah, another person getting burned by the outdated design doc ;)
Can we please update the doc? Or at least remove the auth/authz
section and place a TBD in there?
> Subversion (Server side) provided for Authorization only.
> However, I've only been able to find authentication code and that code
> appeared to be client stuff only. I haven't found any code implementing
> 22.214.171.124 of the design document. A previous thread lead me to believe
> that commit hooks are the way to handle authorization vs what is
> discussed in 7.2... The only authorization I've been able to track down
> was the Apache based methods. Does Subversion authorize for local
> access? Hooks are fine for me but the Subversion MO makes me think that
> there is an API I'm missing. What about the ACLs I've seen mentioned in
> a few threads?
There were several quite long threads about this on the mailinglist.
Please search the archives and seek them out. ACLs are not scheduled
for 1.0 IIRC. We do have consensus with respect to needing ACLs at some
> I actually started to develop an Apache 2.0 module to handle all of this
> outside of subversion. I have stopped for the time being as It seemed
> like I was heading in the wrong direction. I need it for something else
> I'm doing, so I will complete it at some point.
There are some issues with respect to doing fine grained access control
with Apache. Greg Stein and I tried to come up with an Apache configuration
that did fine grained access control, but we got bitten by the so
called '$svn' url.
> Please Please clarify this whole thing for me folks.
The current status is that ACLs are put on hold for now. But ofcourse
anyone with enough time could provide patches ;)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu May 23 09:45:31 2002