Re: Problem with 'cvs login'
Christopher Faylor wrote: On Tue, Apr 26, 2005 at 06:15:14PM -0700, Brian Dessent wrote: Christopher Faylor wrote: If that really does fix the problem then something is broken in CYGWIN. Corinna fixed things so that this should no longer be a problem: http://sources.redhat.com/ml/cygwin-announce/2004-11/msg00014.html I tested this here and I can confirm that SYSTEMROOT indeed is not being set in the child if it's not included in 'passenv'. I'll see if I can dig further... I checked in a fix for this last night. Screw the gold star! The Gilded Lantern Award For Meritorious Service (GLAFMS) to none other than cg(PR)f aka cfprg aka cfPaulReveref aka The dead of night no less! (Even still, I can hear the clopety clop of the keyboard as night settles over the puter.) Sincerely, thanks cg(PR)f for all you do. Regards, L Anderson -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
On Tue, Apr 26, 2005 at 06:15:14PM -0700, Brian Dessent wrote: Christopher Faylor wrote: If that really does fix the problem then something is broken in CYGWIN. Corinna fixed things so that this should no longer be a problem: http://sources.redhat.com/ml/cygwin-announce/2004-11/msg00014.html I tested this here and I can confirm that SYSTEMROOT indeed is not being set in the child if it's not included in 'passenv'. I'll see if I can dig further... I checked in a fix for this last night. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
Rancier, Jeff wrote: |passenv = PATH I don't know if this applies in your situation, but if xinetd is stripping SYSTEMROOT from the child process' environment, then all socket functions in that process will fail. I think recent versions of the cygwin1.dll have measures to prevent this from happening, but just for grins try adding SYSTEMROOT to the above and see if it makes any difference. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Problem with 'cvs login'
Instead of PATH? Thanks for the reply, BTW. -Original Message- From: Brian Dessent [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 5:43 PM To: cygwin@cygwin.com Subject: Re: Problem with 'cvs login' Rancier, Jeff wrote: |passenv = PATH I don't know if this applies in your situation, but if xinetd is stripping SYSTEMROOT from the child process' environment, then all socket functions in that process will fail. I think recent versions of the cygwin1.dll have measures to prevent this from happening, but just for grins try adding SYSTEMROOT to the above and see if it makes any difference. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
Rancier, Jeff wrote: (please don't TOP QUOTE) I don't know if this applies in your situation, but if xinetd is stripping SYSTEMROOT from the child process' environment, then all socket functions in that process will fail. I think recent versions of the cygwin1.dll have measures to prevent this from happening, but just for grins try adding SYSTEMROOT to the above and see if it makes any difference. Instead of PATH? Thanks for the reply, BTW. No, add SYSTEMROOT to the list. passenv = PATH SYSTEMROOT Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Problem with 'cvs login'
Thanks Brian, That resolved that issue, as far as I can tell, now I'm getting the following: $ cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot login Logging in to :pserver:[EMAIL PROTECTED]:2401/usr/local/cvsroot CVS password: cvs login: authorization failed: server jrancier rejected access to /usr/local/cvsroot for user jrancier I did a chmod 777 on /usr/local/cvsroot, stopped and started xinetd, but still get the same. Any other suggestions? Thanks, Jeff -Original Message- From: Brian Dessent [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 5:43 PM To: cygwin@cygwin.com Subject: Re: Problem with 'cvs login' Rancier, Jeff wrote: |passenv = PATH I don't know if this applies in your situation, but if xinetd is stripping SYSTEMROOT from the child process' environment, then all socket functions in that process will fail. I think recent versions of the cygwin1.dll have measures to prevent this from happening, but just for grins try adding SYSTEMROOT to the above and see if it makes any difference. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
Rancier, Jeff wrote: That resolved that issue, as far as I can tell, now I'm getting the following: $ cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot login Logging in to :pserver:[EMAIL PROTECTED]:2401/usr/local/cvsroot CVS password: cvs login: authorization failed: server jrancier rejected access to /usr/local/cvsroot for user jrancier I did a chmod 777 on /usr/local/cvsroot, stopped and started xinetd, but still get the same. Any other suggestions? Did you create the password file /usr/local/cvsroot/CVSROOT/passwd and allow access for 'jrancier'? By the way, you don't have to go through all the trouble of setting up pserver if you just want a local CVS repository. Just set $CVSROOT and use normal cvs commands, and it will access the files locally. pserver is fairly insecure and if you plan to access it remotely you should use the CVS_RSH=ssh access method instead. About the only thing pserver is useful for is if you want a publicly available anonymous read-only repository. My apologies if you knew this already. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Problem with 'cvs login'
I want to provide access to the respository remotely and for other users. No, while reading the FAQ, I was under the impression it would be created the first time, just use mkpasswd? Didn't know all that, that's for the info. Jeff -Original Message- From: Brian Dessent [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 6:38 PM To: 'cygwin@cygwin.com' Subject: Re: Problem with 'cvs login' Rancier, Jeff wrote: That resolved that issue, as far as I can tell, now I'm getting the following: $ cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot login Logging in to :pserver:[EMAIL PROTECTED]:2401/usr/local/cvsroot CVS password: cvs login: authorization failed: server jrancier rejected access to /usr/local/cvsroot for user jrancier I did a chmod 777 on /usr/local/cvsroot, stopped and started xinetd, but still get the same. Any other suggestions? Did you create the password file /usr/local/cvsroot/CVSROOT/passwd and allow access for 'jrancier'? By the way, you don't have to go through all the trouble of setting up pserver if you just want a local CVS repository. Just set $CVSROOT and use normal cvs commands, and it will access the files locally. pserver is fairly insecure and if you plan to access it remotely you should use the CVS_RSH=ssh access method instead. About the only thing pserver is useful for is if you want a publicly available anonymous read-only repository. My apologies if you knew this already. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
Rancier, Jeff wrote: I want to provide access to the respository remotely and for other users. No, while reading the FAQ, I was under the impression it would be created the first time, just use mkpasswd? Didn't know all that, that's for the info. If you are providing write (commit) access then you should not use pserver, it sends passwords in plaintext. Use ssh. It's even simpler to setup because sshd uses the built in windows user accounts, whereas CVS pserver requires you to maintain a seperate set of accounts. I think you're confusing the two passwd files. One is /etc/passwd which is created by the Cygwin command mkpassd, and should be created automatically when you first log on after installing Cygwin. This is the standard unix passwd file and is used by many commands. The CVS passwd file is $CVSROOT/CVSROOT/passwd and is a completely different file, with a different format, that is only used by CVS. You must create and maintain this file yourself. Section 2.9.4.1 of the CVS manual tells you all about this. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
On Tue, Apr 26, 2005 at 02:43:06PM -0700, Brian Dessent wrote: Rancier, Jeff wrote: |passenv = PATH I don't know if this applies in your situation, but if xinetd is stripping SYSTEMROOT from the child process' environment, then all socket functions in that process will fail. I think recent versions of the cygwin1.dll have measures to prevent this from happening, but just for grins try adding SYSTEMROOT to the above and see if it makes any difference. If that really does fix the problem then something is broken in CYGWIN. Corinna fixed things so that this should no longer be a problem: http://sources.redhat.com/ml/cygwin-announce/2004-11/msg00014.html cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Problem with 'cvs login'
Although I still can't login with my login (I found an old .cvspass for which I knew the password). BTW can someone point me a utility to create one which will work for CVS. When I try to change my passwd for bash, via passwd, it declares I'm not a valid user, although I'm in /etc/passwd). I removed the SYSTEMROOT entry from the passenv line in my /etc/xinetd.d/cvspserver, recycled xinetd, and attempted an anonymous login and it failed as before. Changed it back, and it worked. Here's the screenshot: , | [EMAIL PROTECTED] ~ | $ ps -ef | UID PIDPPID TTY STIME COMMAND | jrancier1388 1 con 19:53:15 /usr/bin/bash | jrancier17681388 con 19:53:52 /usr/bin/ps | | [EMAIL PROTECTED] ~ | $ /usr/local/bin/xinetd.start | | [EMAIL PROTECTED] ~ | $ cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot login | Logging in to :pserver:[EMAIL PROTECTED]:2401/usr/local/cvsroot | CVS password: | cvs [login aborted]: reading from server: Software caused connection abort | | [EMAIL PROTECTED] ~ | $ ps -ef | UID PIDPPID TTY STIME COMMAND | jrancier1388 1 con 19:53:15 /usr/bin/bash | SYSTEM 988 1 ? 19:53:59 /usr/sbin/xinetd | jrancier16281388 con 19:54:59 /usr/bin/ps | | [EMAIL PROTECTED] ~ | $ kill 988 | | [EMAIL PROTECTED] ~ | $ /usr/local/bin/xinetd.start | | [EMAIL PROTECTED] ~ | $ cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot login | Logging in to :pserver:[EMAIL PROTECTED]:2401/usr/local/cvsroot | CVS password: | | [EMAIL PROTECTED] ~ | $ ` Jeff -Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 26, 2005 7:06 PM To: cygwin@cygwin.com Subject: Re: Problem with 'cvs login' On Tue, Apr 26, 2005 at 02:43:06PM -0700, Brian Dessent wrote: Rancier, Jeff wrote: |passenv = PATH I don't know if this applies in your situation, but if xinetd is stripping SYSTEMROOT from the child process' environment, then all socket functions in that process will fail. I think recent versions of the cygwin1.dll have measures to prevent this from happening, but just for grins try adding SYSTEMROOT to the above and see if it makes any difference. If that really does fix the problem then something is broken in CYGWIN. Corinna fixed things so that this should no longer be a problem: http://sources.redhat.com/ml/cygwin-announce/2004-11/msg00014.html cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
Brian Dessent wrote: [snip] If you are providing write (commit) access then you should not use pserver, it sends passwords in plaintext. Use ssh. It's even simpler to setup because sshd uses the built in windows user accounts, whereas CVS pserver requires you to maintain a seperate set of accounts. Nope. The use of CVS's password file is optional, you can even have some users with regular accounts and some without, but if you want to give read only access you must define that in CVS's password. I think you're confusing the two passwd files. One is /etc/passwd which is created by the Cygwin command mkpassd, and should be created automatically when you first log on after installing Cygwin. This is the standard unix passwd file and is used by many commands. Including cvs under any UNIX implementation; I use it under Solaris and Linux. The CVS passwd file is $CVSROOT/CVSROOT/passwd and is a completely different file, with a different format, that is only used by CVS. You must create and maintain this file yourself. Section 2.9.4.1 of the CVS manual tells you all about this. Each repository can have its own users. But the point is: is Cygwin's port of CVS different than the regular CVS we use under UNIX? The difference being that under Cygwin you must create your own repository password file (I use cvsadmin, a separate program, to do that BTW). -- René Berber -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
René Berber wrote: But the point is: is Cygwin's port of CVS different than the regular CVS we use under UNIX? The difference being that under Cygwin you must create your own repository password file (I use cvsadmin, a separate program, to do that BTW). The CVS that is packaged with Cygwin is the same CVS that is standard on all unix systems, as far as I know. What I don't know is if 'fallback' authentication works. If you have a valid /etc/passwd file, and the user/password combination exists as a valid Windows user with that password, then it ought to. But, if CVS is looking to find a crypted password in /etc/passwd then it won't work, because that's not how windows stores passwords. If it doesn't, then you'll have to create a CVS passwd file and use the 'crypt' utility to get the crypt()-ed password. The reason I recommended ssh was that I know for sure that its authentication works fine against the windows users and their passwords, so using it would be both more secure and easier to setup (no duplication of accounts between windows users and CVS passwd.) But, if you don't want cvs users to map onto actual users, then using CVS passwd would be better. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with 'cvs login'
Christopher Faylor wrote: If that really does fix the problem then something is broken in CYGWIN. Corinna fixed things so that this should no longer be a problem: http://sources.redhat.com/ml/cygwin-announce/2004-11/msg00014.html I tested this here and I can confirm that SYSTEMROOT indeed is not being set in the child if it's not included in 'passenv'. I'll see if I can dig further... Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
