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

broken AuthzSVNAccessFile in 1.3.0 ?

From: Michal Levý <michal.levy_at_mediaresearch.cz>
Date: 2006-01-17 11:26:59 CET

Hello

After installing svn 1.3.0 and upgrading Apache from 2.0.54 to 2.0.55
(on Windows Server 2003), there are some strange behavior in
authorization....

Apache conf:
<Location /svn/>
   DAV svn
   SVNParentPath C:\Data\SVN
   SVNListParentPath on
   AuthType Basic
   AuthName "Subversion repositories"
   AuthUserFile svn_passwd
   AuthzSVNAccessFile svn_access.conf
   Require valid-user
</Location>

svn_access.conf: (relevant part of it)

[groups]
admins = Liwoj
devs = Liwoj, peta, Miroslav, arthur, pavca

[/]
* = r
@admins = rw
[TVM:/]
@devs = rw

Problem description:
Before upgrade (svn 1.2.3.) everything worked like a charm.
After upgrade when someone from devs group try to commit anything to TVM
   repository, he gets this error message " Error: MKACTIVITY of
'/svn/tvm/!svn/act/7dff391b-9d6b-0d4c-a0a5-6cf978297dda': 403 Forbidden
(http://stoupa:8080)"
Message in Apache error log is: "[Tue Jan 17 11:02:15 2006] [error]
[client 192.168.0.1] Access denied: 'peta' MKACTIVITY tvm: "
Removing trailing slash from [TVM:/] do not help.
Removing trailing slash from "<Location /svn/>" do not help either
(added for SVNListParentPath to work)
I (Liwoj) can commit without problems. When i change root privileges from
"* = r" to "* = rw", all @devs can commit normally.

Is that bug or by design ?

Thanks

-- 
--
Michal Levý aka Liwoj
michal.levy@mediaresearch.cz
ICQ# work: 118679657 home: 32598354
GSM# +420775988024
==== Codito, ergo sum. =====
=== I code, therefore I am ===
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 17 11:41:44 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.