From owner-freebsd-stable@FreeBSD.ORG Tue Apr 15 17:45:05 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 B78DE37B401 for ; Tue, 15 Apr 2003 17:45:05 -0700 (PDT) Received: from util.inch.com (ns.inch.com [216.223.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 365DD43FBF for ; Tue, 15 Apr 2003 17:45:04 -0700 (PDT) (envelope-from spork@inch.com) Received: from shell.inch.com (inch.com [216.223.192.20]) h3G0j2Hc017111; Tue, 15 Apr 2003 20:45:02 -0400 (EDT) (envelope-from spork@inch.com) Received: from shell.inch.com (localhost [127.0.0.1]) by shell.inch.com (8.12.8/8.12.8) with ESMTP id h3G0j25d057132; Tue, 15 Apr 2003 20:45:02 -0400 (EDT) (envelope-from spork@inch.com) Received: from localhost (spork@localhost)h3G0iuDN057122; Tue, 15 Apr 2003 20:45:01 -0400 (EDT) X-Authentication-Warning: shell.inch.com: spork owned process doing -bs Date: Tue, 15 Apr 2003 20:44:56 -0400 (EDT) From: Charles Sprickman To: Doug Silver In-Reply-To: <200304151618.21167.dsilver@urchin.com> Message-ID: <20030415204211.I6307@shell.inch.com> References: <200304151126.21202.dsilver@urchin.com> <200304151618.21167.dsilver@urchin.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org 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: Wed, 16 Apr 2003 00:45:06 -0000 On Tue, 15 Apr 2003, Doug Silver wrote: > 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. That would be the problem. You probably lack the crypto libs needed to check the "old" users. The new users are probably using a different encryption method in the password file. Look at /etc/master.passwd and you should see a difference in the crypted password. As far as I know, you *can't* pull libcrypto out and replace it from ports as there is no such port... I'm sure someone will correct me if I'm wrong about that, but even if I am, it still sounds like a bad idea. Charles > 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 > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >