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.
Matthias Mohr wrote: > Now it works !!!!!! > > >>After this the passwd file would look like: >>MyCVSlogin:#@k7r3!fgrwk:MyNTUser >>Where the first part is the new cvs login and the middle part is the cvs password >>(encrypted) for this login and the third part is the valid NT user login to be used >>as alias when MyCVSlogin connects. >> > I removed the middle-part (the password) by hand (with an text editor), > so it will look like this: > MyCVSlogin::MyNTUser > > That's what I wanted :-) > But it only works with the pserver-protocol, not with the sspi-protocol: > C:\> cvs -d :sspi:MyCVSLogin at cvssrv:/Repository login > Logging in to :sspi:MyCVSLogin at cvssrv:2401/Repository > CVS password: ValidNTUserPassword > cvs [login aborted]: : Authentication failed cvs -d :sspi:MyNTUser at cvssrv:/Repository login :pserver: is the only protocol that uses the passwd file. :sspi: mode authenticates you using your domain/machine credentials. So, yes, this is a "feature". BTW, If your users can use :sspi: then why do you need :pserver:? - Brian _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs