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.
Should have stated our setup: We are on a tightly locked down intranet with basically no Internet access except http (port 80) and this is authenticated too. We use two access methods: sspi for all PC developers pserver for two developers on Sun Solaris So I figured I could deploy a minimalistic set of files supporting only these protocols. Anyway I will have a stab att Oliver's install script and see if I can make a CVSNT client only installer based on that an my own information. Oliver, there are some files in your setup that I don't think are needed anymore. I removed them from my version a while ago as I looked in the MSI script source Tony uses (I am diffing every time he changes this). More info at home.... Best regards, Bo Berglund -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Mike Wake Sent: den 25 januari 2006 16:51 Cc: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: [cvsnt] Exactly which CVSNT files are needed for a client only??? Bo Berglund wrote: > These are the ones I moved: > > ca.pem You need this if you ever want to use sserver. > COPYING You need this, otherwise you are being naughty. > cvsnt-default.pem You need this if you ever want to use sserver. > extnt.exe > extnt.ini You need these if you ever want to use Eclipse or ssh. > genkey.exe Might need this for some setups of sserver... Self signing certificates and stuff. > Release Notes.rtf Couldn't hurt. _______________________________________________ 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