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

Re: CVS/SVN comparison

From: David F. Newman <dnewman_at_epnet.com>
Date: 2004-10-22 20:26:46 CEST

On Fri, 2004-10-22 at 13:37, Scott Palmer wrote:
>
> I was under the impression that using svn: the only security was
> read-only vs. read-write for the whole repository, and that you could
> not apply different security based on the path. So with svn: the
> 'tags' folder can't be made read-only independently of the trunk and
> other 'copies'.
>
> From the Subversion book:
> "Notice that svnserve only understands “blanket” access control. A
> user either has universal read/write access, universal read access, or
> no access."

The key word here is "svnserve". There are other repository access
methods.

> So I think my claim still stands.
>

If you continue reading into the next section you will see that you have
fine grained access control when utilizing an Apache web server for
repository access. The apache server provides the user authentication
while the subversion module mod_authz_svn provides the access control on
a per directory basis.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 22 20:27:15 2004

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.