Could you please be more precise? svn+ssh:// is completely fine (if you configure authorized_keys(5) correctly), it's admins who give their users filesystem write access to the repository directory who are the problem.
Nico Kadel-Garcia wrote on Sat, Jul 02, 2011 at 11:59:44 -0400: > On Fri, Jul 1, 2011 at 11:26 AM, Geoff Hoffman > <ghoff...@cardinalpath.com> wrote: > > > >> 3. What is the best way to lock the Trunk so only certain users can access > >> it, using Hook Script or using admin tool? > > > > > >> > >> use Subversion's built-in path-based authorization or > >> possibly some Apache configuration tweaks > > > > > > I just followed this guide yesterday, coincidentally, and it worked > > perfectly > > http://davidwinter.me/articles/2006/03/03/access-control-for-subversion-with-apache2-and-authz/ > > > > Not that it's utterly useless for file:/// or svn_ssh:/// based > access, and if you support those separate access methods in parallel > or instead of HTTP/WebDAV based access, you'll need to rethink your > acess control.
