Nathan Kidd wrote:
> Andy Levy wrote:
>> On 6/21/07, Andreas Hasenack <andreas@mandriva.com.br> wrote:
>>> Is it possible to control read access with these repository access
>>> modes? file:// and svn+ssh://
>> There is no way to control access when using file://. Anyone who has
>> access to the repository has access to the WHOLE repository, and even
>> more importantly, they require direct permissions at the filesystem
>> level for the actual repository DB - which means that anyone can
>> corrupt or destroy your entire repository very, very easily.
>
> ...but for svn+ssh:// (which is svnserve) you can do what you want using
> the authz file, supported since 1.3.
> http://subversion.tigris.org/svn_1.3_releasenotes.html
In addition, with svn+ssh:// you can limit those users (if you use
public keys) to only being able to run the svnserve program. So even
though those accounts have permissions at the file system level to the
actual repository DB - you don't have to give them the ability to login
and get a shell.
http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks
That limits the amount of damage that a user can do, unless they figure
out some way to get access to the server's file system.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 22 00:00:25 2007