Authorisation broken in SVN 1.0.0?

["Schmitt, Michael" <m....@fgan.de>]

Hello,

the CHANGES file of Subversion 1.0.1 lists the following bug fixes:

 * allow anonymous access checking in mod_authz_svn
 * fixed: mod_authz_svn now works with SVNParentPath (issue #1588)

Does that mean that option "AuthzSVNAccessFile ..." does not work in
combination with "SVNParentPath" (i.e. multiple repositories) and/or
option "Satisfy Any" in 1.0.0? (This could explain the problems I have
with enforcing read/write restrictions.)

BTW: Has anybody prepared Windows binaries for SVN 1.0.1?

Michael

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

RE: Authorisation broken in SVN 1.0.0?

[Sander Striker <st...@apache.org>]

> From: Schmitt, Michael [mailto:m.schmitt@fgan.de]
> Sent: Monday, March 22, 2004 3:02 PM

> Hello,
> 
> the CHANGES file of Subversion 1.0.1 lists the following bug fixes:
> 
>  * allow anonymous access checking in mod_authz_svn
>  * fixed: mod_authz_svn now works with SVNParentPath (issue #1588)
> 
> Does that mean that option "AuthzSVNAccessFile ..." does not work in
> combination with "SVNParentPath" (i.e. multiple repositories)

Correct.

> and/or option "Satisfy Any" in 1.0.0?

The Satisfy Any config example is unfortunately somewhat broken
in 1.0.1 too.  You will consistently get (no author) on every
commit.  This is fixed on trunk, and is proposed for backport
to 1.0.2.

> (This could explain the problems I have with enforcing read/write
> restrictions.)
> 
> BTW: Has anybody prepared Windows binaries for SVN 1.0.1?

Not yet.  I was supposed to get around to that last weekend,
but didn't.


Sander

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