Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
>> I have a cvsnt server installed on a Win2k system, and usually advise my >> users to use the sspi protocol. That works fine as long as they are on a >> Windows machine. But I have two problems with this configuration: >> >> 1- What do I tell Linux users? I also have installed the ssh protocol. Does >> it simply work, so to speak "out of the box"? Or is some other installation >> on the server (ssh client) necessary for that? > > There is a SSPI client-only protocol that works under linux, so they can > connect directly with sspi. Are you saying that a Linux user could connect with something like cvs -d :sspi:user at myhost:/myrepo login and it would work? > SSH server requires an SSH server on the server (sounds redundant...), > which isn't perfect or trivial under Windows. Search the archives here I did that, and as you say, it doesn't look trivial. I also haven't yet found something good about the interaction between cvsnt and ssh. It also seems that I've read that with ssh, cvsnt can't run as a service. So if there was a different means, that would be cool. >> 2- It seems that clients that run on Win9x systems use non-encrypted >> communication when connecting through sspi. Is there a protocol that's easy >> to install and configure for this platform that's encrypted? > > I think sserver will work that way, and AFAIK it's easy to use with > CVSNT. Win9x systems aren't as secure--but I think you might run into > that trouble with the Linux SSPI client as well??? Thanks. I'll look into the sserver protocol. Gerhard