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

Re: Controlling update and/or commit access to a repository URL

From: Edward Diener <ediener_at_loyaltyworks.com>
Date: 2004-09-03 23:44:58 CEST

"Lee Merrill" <LeeMerrill@bustech.com> wrote in message
> Hi Edward,
> Yes, you can do this, though it's not built into the repository, it
> can be done in the web server, see this link for more information:
> http://svnbook.red-bean.com/svnbook/ch06s04.html#svn-ch-6-sect-4.4

This requires Apache. Unfortunately we are currently using svn server. I
will have to convince my company to use Apache for SVN in order to provide
this functionality.

> It could also be done via a start-commit hook script, to check the
> user and the directories being modified, to see if they are authorized
> to make those changes:
> http://svnbook.red-bean.com/svnbook/ch05s02.html#svn-ch-5-sect-2.1

This looks better when if Apache is not being used, but does not allow me to
protect a user from read access to a repository.

While both are viable possibilities has there really been no impetus from
users of SVN to have SVN provide this feature itself. Clearly svn client
could theoretically be updated to accept 'include' or 'exclude' lists of
usernames for each of its repository directories and/or permissions for each
user, to be administered through an administrator via some sort of protected
server side files. This would put access control in the hands of svn itself.
Has this been a topic which others have discussed or requested for future
versions of SVN at all ? It does seem that within any SCCS system that the
system itself should provide easy functionality for restricting or allowing
access to directories/files within it. Perhaps the answer to that from SVN
has always been, use Apache it's free. But that does not make configuring
such functionality as easy as it could be made from within svn itself
through its own internal mechanisms. I am thinking of the fact that if some
sort of configuration existed on the SVN server for allowing or restricting
access, then the svn client command could easily access this information and
allow or deny users the ability to carry out access to certain directories
in a repository.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 3 23:45:52 2004

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