[cvsnt] Re: New Bugs - Upgrading from CVSNT 2.5.01 (Travis) Build 1976 to CVSNT 2.5.02 (Servalan) Build 2115

Jeff Lewis jdlewis at xactware.com
Mon Oct 17 16:42:39 BST 2005


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.


Just an additional note on all of this, when commit a change with
2.5.02, the user name that gets logged on the revision is the domain
user whether or not the user name is included in the CVSROOT variable.
Version 2.5.01 didn't do that.  

Even though I haven't given the 2.5.02 client out to anyone yet, all new
check-ins are getting 'ntdomain\user' as the author instead of just
'user' like 2.5.01 used to do...  I also haven't told the users to
change their CVSROOT variable yet...

Thanks,


Jeff Lewis wrote:
> So CVSROOT should be something like:
> set CVSROOT=:sspi:@mycvsserver:c:/cvs
> Instead of 
> set CVSROOT=:sspi:myuser at mycvsserver:c:/cvs
> Is that correct?
> Thanks,

> Tony Hoyle wrote:
> > Jakob Kruse wrote:
> > > I just tried downgrading the server to 2.5.01.1976. It changes the

> > > error, but doesn't seem to remove the problem. Where 2.5.02 would 
> > > give me the "Unknown Error -1" error, 2.5.01 gives me:
> > > 
> > > cvs.exe [checkout aborted]: authorization failed: server
<censored> 
> > > rejected access to /myrepo for user Jakob Kruse
> > > 
> > > Using Tortoise this results in a login prompt, after which
Tortoise 
> > > sends a cvs login command, but the error just comes again.
> > > 
> > This is the problem with using usernames with SSPI.  It's much
better to just let the default authentication handle it.

> > eg. if you're on a laptop for example, which commonly isn't logged
into the domain, if you use foo at server, you'll actually be trying to log
into LAPTOP\foo at server, which is not going to work.

> > Once domain trusts get involved it gets even more complicated...

> > If you let the SSPI negotiation handle it internally it'll log you
in using its already cached credentials for the server, so it's a lot
less error prone.

> > Also, don't use cvs login with sspi unless you absolutely have to..
the system already has your credentials.

> > Tony
_______________________________________________
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



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook