Thomas Robinson wrote on Wed, 1 Oct 2008 at 09:12 -0400:
> I noticed recently on an SVN server that the following occurred (simplified
> example):
>
> On an apache server with integrated windows authentication (
> http://myserver/svn/dev/), I have the following permissions:
>
> [/]
> Thomas = r
>
> [dev:/]
> Thomas =
>
Having both entries won't help debugging.
> [dev:/somecode/]
> Thomas = r
>
> [dev:/someothercode/]
> Thomas =
>
> Then, here is the access I have:
>
> http://myserver/svn/dev/ - Forbidden
> http://myserver/svn/dev/somecode/ - Accessible
> http://myserver/svn/dev/someothercode/ - Forbidden
>
> However, when I insert a "." into the right place in the URL, the following
> happens:
>
> http://myserver/svn/dev./ - Accessible
> http://myserver/svn/dev./somecode/ - Accessible
> http://myserver/svn/dev./someothercode/ - Accessible
>
> The problem appears to be that when that "." is inserted into the URL, then
> the permissions for [/] are used for the entire repository rather than just
> the actual folder permissioning. I have verified by removing the permission
> for [/], in which case, the right folders are forbidden.
>
> Is this a bug? This issue is both in 1.4.2 and 1.5.
>
On Windows, try creating a file and running these two commands:
dir foo.txt.
dir foo.txt
Both commands will work. I'd guess that it's a so-called "feature" of the
OS. But our path parsing code doesn't recognize that, sees that '/dir.'
isn't a subdir of '/dir' and uses the closest parent's perms (in your
case, the root's perms).
And I don't want to think about how to solve it. It makes me feel bad
enough already to know it exists.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-05 21:51:33 CEST