Simon Kitching <simon@ecnetwork.co.nz> writes:
> On Fri, 2004-02-13 at 14:59, Perry E. Metzger wrote:
>> Er, unfortunately, for good or ill, many people need to use
>> ssh. Sometimes this is simple good security sense -- you want to avoid
>> opening additional attack vectors for a machine.
>>
>> Given that, what might I be able to do to tighten down the on-machine
>> security without adding another bunch of code to audit talking
>> off-machine?
>
> The SVN book discusses at length exactly how to provide secure remote
> svn access.
>
> See: http://svnbook.red-bean.com/html-chunk/ch06.html
> and particularly: http://svnbook.red-bean.com/html-chunk/ch06s03.html
Yes, and I'm using such a method: svn+ssh.
Unfortunately it does not do quite what I want. Also, don't tell me
that we have to run "svnserver", since that really isn't the answer
here for our project.
Perry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 13 18:20:06 2004