"pivotgrind" <pivotgrind@hotmail.com> writes:
> thanks for the fast reply... i guess what i meant was tcp/ip compression in
> the sense that cvs uses it. (basically the -z # option). it sounds like
> svn will be just as capable.
>
> another question, are you still planning on implementing the security
> features outlined in the design doc?
>
> thanks again.
> -Isaac
>
> Authorization
> By authorization, we mean answering the question:
>
> "Is user X allowed to perform action Y on data Z?"
>
> The Subversion filesystem provides a single interface for answering this
> question.
Sorry, that part of the design doc is waaaaay old. We use apache to
do authentication, but *authorization* is a different story.
For now, you need to use apache's <Location> directives (in
httpd.conf) to restrict what certain users can and cannot do in the
repository. You can also use pre-commit hook scripts to do the same,
with much finer granularity. But this all has to be done in a
home-made way.
Someday after 1.0, we're thinking about putting real ACLs into the
repository filesystem, provided our heads don't explode while thinking
about it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 26 21:08:27 2002