Date: Tue, 15 Apr 2003 20:44:56 -0400 (EDT) From: Charles Sprickman <spork@inch.com> To: Doug Silver <dsilver@urchin.com> Cc: stable@freebsd.org Subject: Re: Problem logging in after upgrade to 4.8-Stable Message-ID: <20030415204211.I6307@shell.inch.com> In-Reply-To: <200304151618.21167.dsilver@urchin.com> References: <200304151126.21202.dsilver@urchin.com> <200304151618.21167.dsilver@urchin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030415204211.I6307>