I'm currently also evaluating svn+ssh as method for remote access.
Our setup:
Server:
- Windows XP 64 bit Professional
- copSSH 1.4.1 (Windows port of OpenSSH 4.5p1 with security fix)
- Subversion 1.4.2 32 bit
Client:
- Windows 2000 Professional
- TortoiseSVN 1.4.1
- PuTTY 0.5.8 (installed together with puttygen.exe and pageant.exe)
After jumping through a few intellectual hoops in configuring the
SSH server command that is executed on behalf of the incoming requests
correctly, this setup worked, i.e. i was able to establish an SSH
tunnel from the client to the server once the private key file was
imported at the client side.
HOWEVER: My big problem is that access via svn+ssh is *substantially*
slower than access via plain svn, even if the client computer lives
in the same local LAN as the server. So i'm quite reluctant to tell
remote users to use svn+ssh with such a slow performance.
(I find this result rather embarassing given that SVN is supposed
to behave good on slow networks... Well, this probably only tells
me that the problem exists between keyboard and chair...)
Others have reported this already, but those who replied only explained
this with pointing out that windows clients tend to be a lot slower
than linux/unix clients. Even though i sometimes enjoy to join
M$ bashfests, this type of reply does not help much in my setup
because i can not tell the users "go use linux instead of windows".
So, maybe someone else has observed the same problem and/or has
solved it and is willing to share the fix?
Robert
> -----Original Message-----
> From: Duncan Murdoch [mailto:murdoch@stats.uwo.ca]
> Sent: Freitag, 17. November 2006 11:28
> To: Thomas Harold
> Cc: users@subversion.tigris.org
> Subject: Re: accessing svn through internet (svn+ssh)
>
>
> On 11/16/2006 10:44 PM, Thomas Harold wrote:
> > 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?
>
> I do use Cygwin's sshd for other things, and it works fine. However, I
> don't have any svn repositories on Windows machines so I can't say for
> sure that would work: I just can't think of any reason why it wouldn't.
>
> Duncan Murdoch
> >
> > (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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 12:05:09 2006