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.
Hmmm. I'm new to CVS. >>Why don't you just use :sspi: (i.e. NTLM2 IIRC) or :gserver: (i.e. Kerberos/AD) ? So :sspi is easier? I'll give it a try. How do I support my Linux and Unix users that are outside our corporate firewall? These guys WILL not develop code on a Win platform. Absolutely refuse to do so. >>Another secure alternative for non-Windows clients would be :sserver: (i.e. SSL). In regard to SSL, I can't a CVS client that actually supports SSL. Or maybe the documentation I have is just poorly written. Yeah, I would love to use SSL, should be more universal. Do you know of a client that supports it? >>Also, running SSH for a CVS server on Windows has several issues,... Is this in fact true? I have been logging in to CVSNT via the Cygwin server for a few days now. The SSH mode is still password authentication, but it seems to handling the protocol. So your telling me that even though the user is "kdwoell", and even if I set NTFS pemissions such that "kdwoell" cannot get CVS access to a particular folder, the SSH authentication takes precedence and the NTFS permissions are ignored? -----Original Message----- From: Oliver Giesen [mailto:ogware at gmx.net] Sent: Friday, December 19, 2003 6:25 AM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: [cvsnt] Latest CVSNT and Windows Server 2003? Woellert, Kirk D. wrote: > Yep, had it running for serveal weeks now (lastest version of CVSNT). > Pserver is up and running and WinCVS and SmartCVS seem to authenticate > against domain users just fine. I had to set up a fully qualified > Active Directory (which I last played with almost 3 years ago). Just > make sure you create a User via the Active Directory interface, then > include that user as a member in the group, Domain Users. > > I'm having trouble getting SSH up and working (no password prompt > style). You have to install Cygwin since G.D. Bill Gates didnt > include an SSH server in WinServ 2003. Why don't you just use :sspi: (i.e. NTLM2 IIRC) or :gserver: (i.e. Kerberos/AD) ? These should be the more natural choices in the kind of environment you describe. Even if you have to provide access to non-Windows clients, you could still let the Windows-clients access the server via these native protocols (and IIRC, gserver should be available for *ix-clients as well). There's nothing that beats SSPI in ease of setup while at the same time providing high-security authentication. Another secure alternative for non-Windows clients would be :sserver: (i.e. SSL). Also, running SSH for a CVS server on Windows has several issues, most prominently the fact that all repository access will ultimately happen as SYSTEM which, apart from the inability to control individual access permissions, gives you no chance to evaluate logs by authors later on. Cheers, -- Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742) _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs