RE: Re: bad access methods (was: 100% repeatable repo wedging)

> -----Original Message-----
> From: Adam Gibson [mailto:agibson@ptm.com]
>
> Why not use ssh+svnserve instead. Use the --listen-host
> option to svnserve so that it only listens on the loopback
> interface(127.0.0.1) so that remote users can not connect to
> the daemon unless they use the forwarding ability of ssh (-L option).
>
> That would seem to make configuration of the server easy(no
> permission problems since only the user account that you use
> to launch svnserve will need permissions to the files) and
> only allow ssh access remotely.

Because most of my developers are on Windows. They don't want to muck
around with ssh port-forwarding (or rather, I don't want them to,
because half of them don't even have a clue what ssh is). TortoiseSVN
has nice built-in support for svn+ssh, no need to mess around with ssh
directly.

-- 
Jarod C. Wilson, RHCE
System Administrator
VoiceBox Technologies
jarod@voicebox.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org