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 email@example.com.
Arthur, I have pserver disabled on our cvs server because we only want to use Domain users and not users from passwd. I do, however, have sserver enabled and using the :sserver: protocol DOES WORK! Any ideas on where to go from here to fix sspi? I've been using sspi because: 1. I can do CVSROOT=:sspi:cvs.mydomain.com:/cvsroot/repo1 to always have my Windows User be used as the user. (very useful when we login to a production box and want to do an update (i.e. we use CVS as a deployment tool as well)) 2. I can also do CVSROOT=:sspi:MYDOMAIN\anotheruser at cvs.mydomain.com:/cvsroto/repo1 to have my working directory always operate under a different user. (useful when working from a laptop or off-domain box) 3. It's secure and works over the Internet 4. It allows me to use real NTFS permissions on the CVS Server to control access to my repositories. For example, I have Windows Domain Groups: CvsUsersRO-repo1 CvsUsersRW-repo1 CvsUsersRO-repo2 CvsUsersRW-repo2 ... When I setup a new repository on our CVSNT Server, I have scripts which correctly setup the NTFS permissions so that users of repo1 cannot access repo2. Do you know if the sserver protocol impersonates the real Windows User and therefore enforces NTFS permissions? Arthur Barrett wrote: > Ryan, > >> CVSROOT=:sspi:cvs.mydomain.com:/cvsroot/repo1 > > Try the following from outside any sandbox, eg: c:\ - I've numbered each > command in case the e-mail comes out with odd linebreaks: > 1. > cvs -d :sspi:cvs.mydomain.com:/cvsroot/repo1 logout > 2. > cvs -d :pserver:cvs.mydomain.com:/cvsroot/repo1 login > Password: <use your windows password> > 3. > cvs -d :pserver:cvs.mydomain.com:/cvsroot/repo1 co -d test > module1/source/VA.MM.Web.Controls/Login > 4. > cd test > 5. > cvs ci -f -m "" Login.cs > 6. > cvs logoiut > > > Does that work? > >> Why is CVS adding a "," prefix to the filename? > > Don't worry about it - it's normal. > >> I don't understand how this is even happening. > > I think it's time to enable clients are allowed to trace server and get > a trace of a working client and a non working one and compare the > results (use winmerge or something) when you find the bits that are > different post the excerpt to the newsgroup. > > Regards, > > > Arthur