I cannot figure out how to restrict permissions on a sub-directory.
What I want is to have anonymous read/write access to everything
except a sub-directory, where only two users have read/write and
everyone else has no access (read or write). I've done a lot of
reading of the manual and googling t
Greetings, Gabriel Ricardo!
> I cannot figure out how to restrict permissions on a sub-directory.
> What I want is to have anonymous read/write access to everything
> except a sub-directory, where only two users have read/write and
> everyone else has no access (read or write). I've done a lot of
briel Ricardo [mailto:gabriel.rica...@gmail.com]
Sent: 16. desember 2009 20:36
To: users@subversion.apache.org
Subject: restricting sub-directory permissions
I cannot figure out how to restrict permissions on a sub-directory.
What I want is to have anonymous read/write access to everything
except
Hi,
Gabriel Ricardo wrote:
> I cannot figure out how to restrict permissions on a sub-directory.
> What I want is to have anonymous read/write access to everything
> except a sub-directory, where only two users have read/write and
> everyone else has no access (read or write). I've done a lot of
Thanks for all the responses. I tried all of the suggestions, but
unfortunately none of them worked. I also downloaded and installed
subversion 1.6.5, along with apache 2.2.14 to see if maybe I needed
more recent versions. I still have the same strange behavior, where
either the sub-directory a
Hi Jon,
The link you sent was helpful and the final workaround mentioned in
the article seems to work, except one thing...
There seems to be a security hole, which is that web-browsing of the
restricted sub-directory is still possible using the anonymous-open
URL. Thus, the solution does not seem
See my comment on the blog post, Gabriel. Did you actually *test* my
workaround, or are you speculating based on your understanding of the theory
of it. I'm happy to address actual problems found in the workaround --
*very happy*, in fact, since I'm using the workaround myself to protect
private
Ah, thanks for your response. I found my problem. I certainly did
try the workaround, but after your response I thought again about my
testing and setup. A simple oversight skewed my test results. I
first logged into the restricted svn URL using proper
username/password. I then tested the anon
