Someone on the cvsnt list asked about doing this, and it sounds like an
interesting project... basically adding SSPI & SSL to svnserve. I
could lash something together in a couple of hours, probably but reckon
it's better to ask here first & do it properly :)
Presumably this has been thought of, so someone's already gone through
how it should hang together... hardcode it in with #ifdef _WIN32,
loadable shared libraries, or some other method. For cvsnt I had a
group of shared libraries that the program enumerated for protocols to
support.
For the client side, is using svn+sspi:// or just sspi:// prerered? (I'd
guess the svn+... syntax, from looking at the code).
(btw. I would do ssh, for which I have a patched Putty DLL, but you're
already using that for external protocols :/).
In the back of my mind is an idea of writing a CVS Client/Server
Protocol -> svnserve wrapper... sounds easier than the effort currently
required to take cvsnt itself to the next stage (which is ditching RCS,
having reached the limits of its abilities) plus it'd mean I wouldn't be
solely responsible for fixing bugs any more :)))
Is there any code at the moment for gzipping the output and/or
encrypting it? Certainly the gzip would help as checking out the
subversion repository was really slow given that it's mostly text files.
Encryption is switchable with sspi (although it's only really 'secure'
on an Active Directory over kerberos... NTLM is a bit of a joke...
people want it though).
Tony
btw. Forgive the noob questions... I've skimmed the design document but
haven't had time to read it properly yet.
Received on Tue Jul 15 23:12:24 2003