From owner-freebsd-stable@FreeBSD.ORG Tue Apr 15 16:18:16 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 444C137B401 for ; Tue, 15 Apr 2003 16:18:16 -0700 (PDT) Received: from mail.urchin.com (ns2.quantified.com [63.212.171.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75DD843F85 for ; Tue, 15 Apr 2003 16:18:15 -0700 (PDT) (envelope-from dsilver@urchin.com) Received: from support.urchin.com (support.urchin.com [63.212.171.7]) by mail.urchin.com (8.12.9/8.12.1) with ESMTP id h3FNIXuf052219 for ; Tue, 15 Apr 2003 16:18:11 -0700 (PDT) (envelope-from dsilver@urchin.com) Received: from danzig.sd.quantified.net (web.urchin.com [63.212.171.5]) (authenticated bits=0) by support.urchin.com (8.12.8/8.12.6) with ESMTP id h3FNIEsL077168 for ; Tue, 15 Apr 2003 16:18:14 -0700 (PDT) (envelope-from dsilver@urchin.com) From: Doug Silver Organization: Urchin Software Corporation To: stable@freebsd.org Date: Tue, 15 Apr 2003 16:18:43 -0700 User-Agent: KMail/1.5.1 References: <200304151126.21202.dsilver@urchin.com> In-Reply-To: <200304151126.21202.dsilver@urchin.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304151618.21167.dsilver@urchin.com> X-Filter-Version: 1.7 (mail.urchin.com) Subject: Re: Problem logging in after upgrade to 4.8-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2003 23:18:16 -0000 On Tuesday 15 April 2003 11:26 am, Doug Silver wrote: > I upgraded two 4.7 machines yesterday to 4.8-stable and now normal users > can't login (both at the console and ssh). Root logs in okay. I created a > new user and that works. However, the first server I upgraded to 4.8 > hasn't had the same problems. I changed my personal password as root on > one of the problem servers and then I was able to login. Did something > change in the password algorithm to cause this to happen or is it something > else? > > Any suggestions?? > > Thanks. > > -Doug Here's some more information that I realize is probably relevant. I've attempted to strip out the openssl/openssh out of the base system, including libcrypto and libssl so I can track it through the ports area. It would be understandable if all accounts were locked out, but why would root and new users not be affected by whatever is broken? -doug