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

Per-directory access control inconsistency

From: Oscar Fuentes <oscarfv_at_telefonica.net>
Date: 2006-09-30 22:52:34 CEST

I've setup a Subversion server (v 1.4.0) on Win2K, Apache
2.0.59. Then, set per-directory access control as per the instructions
on the Subversion book.

My intent is to completely hide the existence of some directories to
certain users. The directory structure is like this:

/trunk
/trunk/common
/trunk/project1
/trunk/project2
...

All users have access to /trunk/common. User X has access to
/trunk/projectX and should not be allowed to know the existence of
other /trunk/project directories.

First I tried giving access to /trunk for all users and forbidding
access for userX to /trunk/projectY (where X != Y). A svn chechout for
user X gets /trunk/common and /trunk/projectX. No references to other
directories. Good. But svn ls http://host/repo/trunk lists all
directories under /trunk. Bad. IMO this is inconsistent: for a given
user, a directory either fully exists or does not exist at all. For
Subversion, a directory exists depending on the operation the user
requests.

Then tried to give access to userX to just /trunk/common and
/trunk/projectX, but then userX cannot chechout or update both
/trunk/common and /trunk/projectX on a single operation. This is more
than an annoyance: two update operations breaks atomicity.

Any idea on how to setup Subversion for this permission schema?

-- 
Oscar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 30 23:00:46 2006

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