Re: login failure on WindowsNT

2000-10-17 Thread Derek R. Price
[EMAIL PROTECTED] wrote: The method should be in the URI prefix since it really does identify the communication protocol. Save "cvs" for the standard CVS protocol; cvs-p perhaps for pserver, cvs-ssh for SSH, etc. The method name does not belong in the URI body. My thought here was that

Re: login failure on WindowsNT

2000-10-17 Thread Rich Salz
Then cvs:// could mean connect to port 2401 and ask what authentication methods are valid. The server would respond with a list and the client would use whatever it thinks is the most secure to authenticate and set up an encryption stream. Oooh, no, you *DON'T* want to do that -- it's a

Re: login failure on WindowsNT

2000-10-12 Thread Derek R. Price
Pradeep Picardo wrote: The version of cvs we are using on unix here has been hacked. I found out about that only last night. I have rebuilt cvs on windows to pick up the port number from the environment the way our unix version does. Should I pass on the code so it can be incorporated into

Re: login failure on WindowsNT

2000-10-12 Thread Pradeep Picardo
The necessary code is already there in the function start_tcp_server(), it just needs to be 'cut and pasted' into connect_to_pserver(). I'm attaching the output of the diff command to this mail, I believe there's something called 'patch' but I'm a windows guy and am not familiar with the unix

RE: login failure on WindowsNT

2000-10-12 Thread John Scott - Outlook
/client and AIX/server). Regards John Scott. -Original Message- From: Derek R. Price [mailto:[EMAIL PROTECTED]] Sent: 12 October 2000 14:57 To: Pradeep Picardo Cc: [EMAIL PROTECTED] Subject: Re: login failure on WindowsNT Pradeep Picardo wrote: The version of cvs we are using

Re: login failure on WindowsNT

2000-10-12 Thread Derek R. Price
Pradeep Picardo wrote: The necessary code is already there in the function start_tcp_server(), it just needs to be 'cut and pasted' into connect_to_pserver(). Okay, this is basically what I did, but thanks anyhow. Also, when passing diffs, in general a 'diff -c' is required for patch. 'diff

Re: login failure on WindowsNT

2000-10-12 Thread Derek R. Price
Larry Jones wrote: Have you looked at the various proposed patches and related commentary at http://www.cvshome.org/cyclic/cvs/dev-net.html under "Change pserver port"? To add my $.02 to what Jim K. has written there, using an environment variable to specify the port is bletcherous -- the

Re: login failure on WindowsNT

2000-10-12 Thread Derek R. Price
Larry Jones wrote: cvs://method/user@host:port/cvsroot has a / in the "server" part, which isn't allowed; I'd suggest : instead: Didn't remember that. Ok. cvs://method:user@host:port/cvsroot I was hoping to make both 'user' 'method' optional, so, with an optional port, and

Re: login failure on WindowsNT

2000-10-12 Thread rsalz
ntax for things like branches, revisions, etc. *IFF needed.* Hope this helps. /r$ From rsalz Thu Oct 12 17:22:27 2000 From: "Derek R. Price" [EMAIL PROTECTED] Organization: Open Avenue To: Larry Jones [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: login failure on WindowsN

Re: login failure on WindowsNT

2000-10-11 Thread Derek R. Price
Pradeep Picardo wrote: I have (correctly I believe) set the environment variables CVSROOT and CVS_CLIENT_PORT on my Windows machine. CVS_CLIENT_PORT only works with a hacked version of CVS. Are you sure you have one? I can put up the patch if you want it. Derek -- Derek Price

Re: login failure on WindowsNT

2000-10-11 Thread Pradeep Picardo
Hi, Terribly sorry about that. The version of cvs we are using on unix here has been hacked. I found out about that only last night. I have rebuilt cvs on windows to pick up the port number from the environment the way our unix version does. Should I pass on the code so it can be