RE: Demanding Win32 server setup: is there any hope?

I have done all of the stuff that you want to do with Apache 2.0.55 and SVN
1.3.1 with Tortoise 1.3.3.6219 (recently updated Tortoise). We have an
internal CA and use that for creating SSL certificates. It works flawlessly
for our distributed development effors. Users just point to the repository
at "https://...." and that's it. A bonus is that if they want to browse the
repository with nothing but a web browser, they can use the same exact URI
from any computer and see their stuff.

What does not currently work (and I don't know why, and it's not an OS
problem per se) is using client-side certificates for authentication and
authorization. Something's up with WebDAV and I can't tell right now if
it's the Apache config or the SVN-added .so's. I'm still banging my head on
it, hopefully somebody can clue me in...

I prefer Apache over SVNServe and SSH tunneling and etc, but YMMV.

If you have users that will complain unless they get the warm fuzzy feeling
of Visual Studio integration, a company called PushOK makes an SCC provider
that makes SVN look like VSS within the IDE. I prefer Tortoise, but the
PushOK product (~$30) helped get some guys over initial apprehension of
using something so different from VSS.

________________________________

From: Mark McWiggins <mark@IcanFixYourEmail.com> [mailto:Mark McWiggins
<mark@IcanFixYourEmail.com>]

Sent: Friday, May 26, 2006 11:44 PM

To: users@subversion.tigris.org

Subject: Demanding Win32 server setup: is there any hope?

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. 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.

--
Mark McWiggins
425-369-8286 (let ring)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org