On 5/26/2006 11:44 PM, Mark McWiggins wrote:
> Hi All,
>
> I'm working for a client *finally* ready to ditch VSS (hooray!), but
> they're a
> semi-fanatical Windows shop. I therefore need to:
>
> (1) Run SVN server on Windows (no problem -- seems to work fine)
>
> (2) Provide a GUI interface (TortoiseSVN seems to work well enough)
>
> BUT I've had no luck with
>
> (3) Providing secure remote access.
>
> I tried ssh tunneling first, but the book examples show only public key
> logins and I don't think these users will go very well for that. I'd like
> to stick with logins (using sshd from Cygwin on the server) and
> passwords. I've
> done that before and got the login to work fine with an ssh inbound from
> another
> box just to get a terminal prompt. But I didn't see how to set the
> 'command' configuration
> to set the 'svnserve' options for passwords.
>
> So I though I'd try Apache. I thought I had it nailed (even though there
> were several
> pieces to assemble until I found out that the mod_dav.so for Windows
> doesn't work
> with Apache 2.2.2, at least.
>
> I didn't try 2.0.58; should I? I *could* probably get them all to
> install cygwin & do
> the public key thing but would rather not if I can escape this.
Putty can also handle public keys, and serve as the ssh client: it's
probably less trouble to install than Cygwin. (Not that Cygwin is all
that difficult, but it's a lot bigger than Putty, and if someone doesn't
like *nix, they probably won't like Cygwin.)
So if the Apache solution doesn't work out, I'd try Putty.
Duncan Murdoch
> Anybody
> doing this
> with passwords?
>
> Thanks much for any guidance whatsoever -- I'm really looking forward to
> driving
> a stake through VSS's evil heart, but I need (3) to work before I can do
> that.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 27 13:42:21 2006