Duncan Murdoch wrote:
>
> I've found it easier to set up svn+ssh access. No server needed (except
> the sshd server, of course, but it was running for other reasons).
>
I prefer the svn+ssh method as well... not sure how well it would work
with a Windows host though. I guess one could use Cygwin's SSHD?
(We waited until we could install some Linux servers before migrating
away from SOS+VSS.)
The nicest part about the svn+ssh method is the use of public-keys for
authentication which are limited to running the "svnserve -t" command.
Which means I can drastically limit who gets command line access to the
server and I don't worry as much about private keys that don't have
passwords. We even have our web server pushing their log files to
individual SVN repositories (one per server for security) using public
key authentication.
The only downside of svn+ssh is that (at least for TortoiseSVN or maybe
it's a PLink issue) some client tools don't play well with using
alternate ports for the SSH tunnel. So we were forced to pipe 22/tcp to
our internal SVN server instead of using an out of the way port like 28022.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 04:44:51 2006