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

Access control bug in SVN >= 1.5.3

From: Ewgenij Gawrilow <gawrilow_at_math.TU-Berlin.DE>
Date: Thu, 19 Feb 2009 09:48:09 +0100


I've posted the following bug report to dev@ mailing list about a month ago.
As it got no response I'm going to repeat it here.

The bug must have been introduced somewhere between 1.5.3 and 1.5.5, as we've
noticed it after the upgrade of both client and server sides from 1.5.2 to 1.5.5.

For a repository, some users are granted full rw access from the root downwards, while other users
may access only specific subtrees in it. The access.conf looks like this:

@full = user1,user2

@full = rw

otheruser = rw

Now this restricted user can check-out his working copy of /some/path/beneath without problem.
He can also make queries with `svn status -u' or `svn info http://URL' . But an attempt to make an
update of the working copy leads to the following mysterious message:

svn: Server sent unexpected return value (403 Forbidden) in response to
OPTIONS request for 'http://our.server/svn/Repo'

In the server log the following record appears:

Access denied: 'otheruser' OPTIONS Repo:/
Provider encountered an error while streaming a REPORT response. [500, #0]
A failure occurred while driving the update report editor [500, #190004]

It gives the impression that `svn update' tries to access something at the root of the repository,
which it formerly (<=1.5.2) did not need. (We have no external subsets in this repository).
If it is not a bug but a new feature, it effectively renders our permission scheme absolutely useless.

I'll appreciate any suggestions and short-term patches fixing the problem until the next release.
Thank you for your attention!

Ewgenij Gawrilow,
TU Berlin, Dept. of Mathematics


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-19 17:46:03 CET

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.