Re: 5-CURRENT source upgrade path is broken in PAM
On Thu, Mar 07, 2002 at 05:16:52PM +, Mark Murray wrote: Mark Murray [EMAIL PROTECTED] writes: Umm, IIRC 'make world' starts by doing a 'make includes' into /usr/obj, which should take care of this. That is 'make world'. It was broken for make obj make depend make, [...] IMO, the repo-copy is the cleanest, because it solves te above problems in the most canonical way. Please talk to Ruslan about this. I suggested doing just what you're thinking of about a month or two ago, and he rejected it. Ruslan is not writing this code; we are. But Ruslan might have an idea because he has eaten a few dogs on make world issues. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37095/pgp0.pgp Description: PGP signature
5-CURRENT source upgrade path is broken in PAM
Hi, Looks like source upgrade path is broken due to PAM. My system is -CURRENT compiled on 19 February. Please fix. -Maxim === libpam/modules/pam_ftp cc -pipe -O -mpreferred-stack-boundary=2 -march=pentium -I/usr/src/lib/libpam/mo dules/pam_ftp/../../../../contrib/openpam/libpam/include -I/usr/src/lib/libpam/m odules/pam_ftp/../../libpam -c /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c -o pam_ftp.o cc -fpic -DPIC -pipe -O -mpreferred-stack-boundary=2 -march=pentium -I/usr/src/l ib/libpam/modules/pam_ftp/../../../../contrib/openpam/libpam/include -I/usr/src/ lib/libpam/modules/pam_ftp/../../libpam -c /usr/src/lib/libpam/modules/pam_ftp/ pam_ftp.c -o pam_ftp.So /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c: In function `pam_sm_authenticate' : /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c:155: warning: passing arg 3 of `pa m_prompt' from incompatible pointer type /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c:155: warning: passing arg 4 of `pa m_prompt' from incompatible pointer type /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c:155: too many arguments to functio n `pam_prompt' /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c: In function `pam_sm_authenticate' : /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c:155: warning: passing arg 3 of `pa m_prompt' from incompatible pointer type /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c:155: warning: passing arg 4 of `pa m_prompt' from incompatible pointer type /usr/src/lib/libpam/modules/pam_ftp/pam_ftp.c:155: too many arguments to functio n `pam_prompt' *** Error code 1 *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Maxim Sobolev [EMAIL PROTECTED] writes: Looks like source upgrade path is broken due to PAM. My system is -CURRENT compiled on 19 February. Please fix. Please use 'make world' to upgrade your system. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Dag-Erling Smorgrav wrote: Maxim Sobolev [EMAIL PROTECTED] writes: Looks like source upgrade path is broken due to PAM. My system is -CURRENT compiled on 19 February. Please fix. Please use 'make world' to upgrade your system. I'm using `make world' (well buildworld, but it shouln't matter). -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Maxim Sobolev wrote: Dag-Erling Smorgrav wrote: Maxim Sobolev [EMAIL PROTECTED] writes: Looks like source upgrade path is broken due to PAM. My system is -CURRENT compiled on 19 February. Please fix. Please use 'make world' to upgrade your system. I'm using `make world' (well buildworld, but it shouln't matter). To be more crear: those errors are result of doing `make world'. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
On Thu, 7 Mar 2002 13:30:44 +0200 (EET), Maxim Sobolev [EMAIL PROTECTED] said: Maxim Hi, Looks like source upgrade path is broken due to PAM. My Maxim system is -CURRENT compiled on 19 February. Please fix. Could this have anything to do with the fact that, since I built world yesterday, I can't log in as root? -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran ChurchWashburn, Iowa 1L, UST School of Law Minneapolis, Minnesota A witty saying proves nothing. -- Voltaire To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Michael D. Harnois wrote: On Thu, 7 Mar 2002 13:30:44 +0200 (EET), Maxim Sobolev [EMAIL PROTECTED] said: Maxim Hi, Looks like source upgrade path is broken due to PAM. My Maxim system is -CURRENT compiled on 19 February. Please fix. Could this have anything to do with the fact that, since I built world yesterday, I can't log in as root? Bah, just completed `make world' after doing `make includes' and found that I can't login as *any* user, not only root!!! Login just hangs after entering password and nothing goes on. DES! PLEASE FIX THAT FSKING PAM - within a very short timeframe it's the second time I'm having problems due to it and this just isn't acceptable even for -current. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
On 7 Mar 2002, Michael D. Harnois wrote: On Thu, 7 Mar 2002 13:30:44 +0200 (EET), Maxim Sobolev [EMAIL PROTECTED] said: Maxim Hi, Looks like source upgrade path is broken due to PAM. My Maxim system is -CURRENT compiled on 19 February. Please fix. Could this have anything to do with the fact that, since I built world yesterday, I can't log in as root? I can't login as root either, I can only gain root access if I boot into single-user. The login process just eats up all cpu-ressources and the login times out after 300 seconds. A su doesn't work either, of course. Sincerely, Rasmus Skaarup To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Bah, just completed `make world' after doing `make includes' and found that I can't login as *any* user, not only root!!! Login just hangs after entering password and nothing goes on. DES! PLEASE FIX THAT FSKING PAM - within a very short timeframe it's the second time I'm having problems due to it and this just isn't acceptable even for -current. That is _my_ fault, not DES'. It was a crypt() problem which I have fixed. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
I can't login as root either, I can only gain root access if I boot into single-user. The login process just eats up all cpu-ressources and the login times out after 300 seconds. A su doesn't work either, of course. Not a PAM problem, a crypt(3) problem. My fault, and fixed. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Date: Thu, 07 Mar 2002 17:43:26 +0200 From: Maxim Sobolev [EMAIL PROTECTED] Michael D. Harnois wrote: On Thu, 7 Mar 2002 13:30:44 +0200 (EET), Maxim Sobolev [EMAIL PROTECTED] said: Maxim Hi, Looks like source upgrade path is broken due to PAM. My Maxim system is -CURRENT compiled on 19 February. Please fix. Could this have anything to do with the fact that, since I built world yesterday, I can't log in as root? Bah, just completed `make world' after doing `make includes' and found that I can't login as *any* user, not only root!!! Login just hangs after entering password and nothing goes on OK; markm said it was a crypt() problem (that he caused fixed); I'm not going to belabor that. (I will, however, express appreciation for Mark taking the heat: thanks, Mark!) But on the point of folks being unable to login, I'm not seeing the failure here. First, an ssh session: bunrab(4.5-S)[3] _ssh freebeast Enter passphrase for RSA key '[EMAIL PROTECTED]': Last login: Thu Mar 7 08:06:22 2002 from bunrab.catwhiske Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (FREEBEAST) #8: Thu Mar 7 06:49:17 PST 2002 Welcome to FreeBSD! ... You may also use sysinstall(8) to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. freebeast(5.0-C)[1] uname -a FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #8: Thu Mar 7 06:49:17 PST 2002 [EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST i386 freebeast(5.0-C)[2] Now, direct login from the (serial) console: Additional TCP options:. Starting background filesystem checks Thu Mar 7 08:08:23 PST 2002 FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0) login: david Password: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (FREEBEAST) #8: Thu Mar 7 06:49:17 PST 2002 Welcome to FreeBSD! ... You may also use sysinstall(8) to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. freebeast(5.0-C)[1] logout FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0) login: root Password: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (FREEBEAST) #8: Thu Mar 7 06:49:17 PST 2002 Welcome to FreeBSD! ... You may also use sysinstall(8) to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. freebeast# uname -a FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #8: Thu Mar 7 06:49:17 PST 2002 [EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST i386 freebeast# logout FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0) login: As I mentioned, it works for me. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
OK; markm said it was a crypt() problem (that he caused fixed); I'm not going to belabor that. (I will, however, express appreciation for Mark taking the heat: thanks, Mark!) *blush* But on the point of folks being unable to login, I'm not seeing the failure here. You'll only see it if you have the bad version of crypt-md5.c(1.9) and you actually use md5 passwords (the salt begins with $1$ when you look in /etc/master.passwd). The breakage time was less than 24 hours. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Mark Murray wrote: Bah, just completed `make world' after doing `make includes' and found that I can't login as *any* user, not only root!!! Login just hangs after entering password and nothing goes on. DES! PLEASE FIX THAT FSKING PAM - within a very short timeframe it's the second time I'm having problems due to it and this just isn't acceptable even for -current. That is _my_ fault, not DES'. It was a crypt() problem which I have fixed. Ok, I see now. Could we please make a rule to send a heads-up in such cases (i.e. in the cases when some serious misbehaviour was introduced and then fixed shortly). This would save me (and probably others) roughly a hour that I spent debugging what's going wrong. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
That is _my_ fault, not DES'. It was a crypt() problem which I have fixed. Ok, I see now. Could we please make a rule to send a heads-up in such cases (i.e. in the cases when some serious misbehaviour was introduced and then fixed shortly). This would save me (and probably others) roughly a hour that I spent debugging what's going wrong. My apologies. I should have thought to do that. I'll remember if there is a next time ;-) M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Maxim Sobolev [EMAIL PROTECTED] writes: Looks like source upgrade path is broken due to PAM. My system is -CURRENT compiled on 19 February. Please fix. Please use 'make world' to upgrade your system. Its more broken than that. I have a fix. The problem is in the headers; you changed #include pam_mod_misc.h to #include secure/pam_mod_misc.h without ensuring that a (correct) pam_mod_misc.h was in an appropriate secure/ dir. I've just finished fixing this (includes a repo-copy) and it will go in shortly. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Maxim Sobolev [EMAIL PROTECTED] writes: Dag-Erling Smorgrav wrote: Maxim Sobolev [EMAIL PROTECTED] writes: Looks like source upgrade path is broken due to PAM. My system is -CURRENT compiled on 19 February. Please fix. Please use 'make world' to upgrade your system. I'm using `make world' (well buildworld, but it shouln't matter). The error message you're reporting indicates that libpam is being built with the wrong headers. This shouldn't happen during 'make world'. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Mark Murray [EMAIL PROTECTED] writes: The problem is in the headers; you changed #include pam_mod_misc.h to #include secure/pam_mod_misc.h without ensuring that a (correct) pam_mod_misc.h was in an appropriate secure/ dir. Umm, IIRC 'make world' starts by doing a 'make includes' into /usr/obj, which should take care of this. I've just finished fixing this (includes a repo-copy) and it will go in shortly. No repo-copy should be necessary. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Maxim Sobolev [EMAIL PROTECTED] writes: Bah, just completed `make world' after doing `make includes' and found that I can't login as *any* user, not only root!!! Login just hangs after entering password and nothing goes on. DES! PLEASE FIX THAT FSKING PAM - within a very short timeframe it's the second time I'm having problems due to it and this just isn't acceptable even for -current. Please moderate your language and your attitude. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Dag-Erling Smorgrav wrote:
Maxim Sobolev [EMAIL PROTECTED] writes:
Dag-Erling Smorgrav wrote:
Maxim Sobolev [EMAIL PROTECTED] writes:
Looks like source upgrade path is broken due to PAM. My system is -CURRENT
compiled on 19 February. Please fix.
Please use 'make world' to upgrade your system.
I'm using `make world' (well buildworld, but it shouln't matter).
The error message you're reporting indicates that libpam is being
built with the wrong headers. This shouldn't happen during 'make
world'.
Shit Happens[tm]. BTW, why you are ignoring system CFLAGS settings
(optimisations and such) for pam_unix? Please consider attached patch.
-Maxim
--- lib/libpam/modules/pam_unix/Makefile2002/03/07 16:40:34 1.1
+++ lib/libpam/modules/pam_unix/Makefile2002/03/07 16:40:45
@@ -27,7 +27,7 @@
LIB= pam_unix
SHLIB_NAME=${LIB}.so.${SHLIB_MAJOR}
SRCS= pam_unix.c pw_copy.c pw_yp.c pw_util.c ypxfr_misc.c ${GENSRCS}
-CFLAGS=-DYP -Dyp_error=warnx \
+CFLAGS+= -DYP -Dyp_error=warnx \
-I${.OBJDIR} \
-I${.CURDIR}/../../../../libexec/ypxfr \
-I${.CURDIR}/../../../../usr.sbin/vipw \
Re: 5-CURRENT source upgrade path is broken in PAM
Maxim Sobolev [EMAIL PROTECTED] writes: Shit Happens[tm]. BTW, why you are ignoring system CFLAGS settings (optimisations and such) for pam_unix? Please consider attached patch. *I* am not. Learn how to use 'cvs annotate' DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
At 5:43 PM +0200 3/7/02, Maxim Sobolev wrote: Michael D. Harnois wrote: Could this have anything to do with the fact that, since I built world yesterday, I can't log in as root? Bah, just completed `make world' after doing `make includes' and found that I can't login as *any* user, not only root!!! Login just hangs after entering password and nothing goes on. For anyone who is stuck with this problem, note that the problem happens when doing a normal password check. So, you *may* be able to work around this if you have something like authorized keys set up in openssh. Or maybe you can log in as one userid, but not some userid like root (that was my problem -- every userid worked fine except for root). If you're lucky enough to set up 'sudo' for a userid you *can* log into, you may be able to use that to become root. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Mark Murray [EMAIL PROTECTED] writes: The problem is in the headers; you changed #include pam_mod_misc.h to #include secure/pam_mod_misc.h without ensuring that a (correct) pam_mod_misc.h was in an appropriate secure/ dir. Umm, IIRC 'make world' starts by doing a 'make includes' into /usr/obj, which should take care of this. That is 'make world'. It was broken for make obj make depend make, and pam_krb5 was just plain broken (../Makefile.inc had a broken path). I've just finished fixing this (includes a repo-copy) and it will go in shortly. No repo-copy should be necessary. IMO, the repo-copy is the cleanest, because it solves te above problems in the most canonical way. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Dag-Erling Smorgrav wrote: Maxim Sobolev [EMAIL PROTECTED] writes: Bah, just completed `make world' after doing `make includes' and found that I can't login as *any* user, not only root!!! Login just hangs after entering password and nothing goes on. DES! PLEASE FIX THAT FSKING PAM - within a very short timeframe it's the second time I'm having problems due to it and this just isn't acceptable even for -current. Please moderate your language and your attitude. Sorry, I've overreacted - unlikely combination of unfortunate events, ya know. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Mark Murray [EMAIL PROTECTED] writes: Umm, IIRC 'make world' starts by doing a 'make includes' into /usr/obj, which should take care of this. That is 'make world'. It was broken for make obj make depend make, [...] IMO, the repo-copy is the cleanest, because it solves te above problems in the most canonical way. Please talk to Ruslan about this. I suggested doing just what you're thinking of about a month or two ago, and he rejected it. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-CURRENT source upgrade path is broken in PAM
Mark Murray [EMAIL PROTECTED] writes: Umm, IIRC 'make world' starts by doing a 'make includes' into /usr/obj, which should take care of this. That is 'make world'. It was broken for make obj make depend make, [...] IMO, the repo-copy is the cleanest, because it solves te above problems in the most canonical way. Please talk to Ruslan about this. I suggested doing just what you're thinking of about a month or two ago, and he rejected it. Ruslan is not writing this code; we are. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
