From owner-freebsd-current Thu Mar 7 8:31:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 70D2737B417 for ; Thu, 7 Mar 2002 08:31:05 -0800 (PST) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.11.6/8.11.6) with UUCP id g27GUp056795; Thu, 7 Mar 2002 16:30:51 GMT (envelope-from mark@grimreaper.grondar.za) Received: from grimreaper (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.2/8.12.2) with ESMTP id g27GTYRV022943; Thu, 7 Mar 2002 16:29:34 GMT (envelope-from mark@grimreaper.grondar.za) Message-Id: <200203071629.g27GTYRV022943@grimreaper.grondar.org> To: David Wolfskill Cc: current@FreeBSD.ORG Subject: Re: 5-CURRENT source upgrade path is broken in PAM References: <200203071618.g27GIdV23971@bunrab.catwhisker.org> In-Reply-To: <200203071618.g27GIdV23971@bunrab.catwhisker.org> ; from David Wolfskill "Thu, 07 Mar 2002 08:18:39 PST." Date: Thu, 07 Mar 2002 16:29:34 +0000 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message