Re: Restrict read-access of inside part of the repository

On 28 Mar 2003, Ben Collins-Sussman wrote:

Thanks for quick reply!

> And it's very easy for *multiple* opaque urls to map to a single
> resource. There's basically no way for httpd.conf to control
> authorization on this many-to-one mapping.
>
> So the party line has always been: "for fine grained authorization,
> use hook scripts in the repository."
>

This is something that I was afraid about.

> Unfortunately, we don't have any read-hook scripts yet. :-(

Is there anykind of document or plans or something else about this
somewhere?

I have been thinking this, and if there is read-hook, should it be
executed for every descending dir (this would be costly, but this is
probably what should to do)?

I also saw a note about property svn:acl in model.texi, is this still
planned or is the current plan to go with read-hook?

BR, Jani

-- 
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org