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

Re: Trying (failing) to limit access to one user

From: <kmradke_at_rockwellcollins.com>
Date: Tue, 26 Apr 2011 16:45:17 -0500

"Alan M. Evans" <ame1_at_extratech.com> wrote on 04/26/2011 04:26:27 PM:
> Sorry for what must be a simple question; I've googled around and
> read/followed all the examples and docs I can find. There is apparently
> something fundamental that I'm misunderstanding.
> Server is running CentOS 5, Subversion 1.6.15, Apache 2.2.3.
> We have a company-wide repository that all developers have full access
> to. Now the company is bringing in a consultant that is to only have
> access to a single directory.
> Simple enough...
> I added a name and password for the user ("jon") to the password file
> with htpasswd.
> Added AuthzSVNAccessFile to the relevant section of the subversion.conf
> in the httpd/conf.d directory, pointing to the paths file below.
> Created a paths file, starting simple with:
> [/]
> * = rw
> jon =
> Thinking that this would retain everybody's access and disallow jon any
> access at all.
> No dice. jon has full access. If I change the * to my user name ("alan")
> then nobody has any access including myself. So I guess that this has
> something to do with "anonymous" access, which I understand is allowed
> by the wildcard.
> I must not, then, understand what anonymous access means because I
> didn't think we were using it. Everybody in the company has a unique
> name to access the repository and blame tells me who did it.
> So what am I missing? What other info can I provide to help figure it
> out?

I've found using "*" to be non intuitive. Try:


Kevin R.
Received on 2011-04-26 23:45:46 CEST

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.