Re: openssh upgrade breaks login

From: Per Hedeland (per_at_hedeland.org)
Date: 01/25/05 

Date: Tue, 25 Jan 2005 07:33:34 +0000 (UTC)

In article
<41f5cbd2$0$10547$5a62ac22@per-qv1-newsreader-01.iinet.net.au>
dtucker@dodgy.net.au (Darren Tucker) writes:
>In article <2MjJd.7233$xu.4543@fed1read05>, Bob Snyder <What@me.worry> wrote:
>>Whoa. I had earlier tried linking with -lcrypt to no avail. In fact the
>>build links with -lcrypt even without the "LIBS=-lcrypt". But I checked
>>for the $1$ and it was there. I hadn't tried the "--with-md5-passwords"
>>because in the FAQ it looked like that was for Red Hat only. But that
>>fixed it.
>
>Hmm, it does read that way, doesn't it? I'll update the FAQ to make it
>clear that either can be the cause.

Well, as I've pointed out here before, the FAQ entry is rather incorrect
wrt to the root cause in any case - the problem isn't with some OSes
having system libraries that are unable to handle their own passwords (of
course), but with some versions of *OpenSSL*, on some OSes, providing a
version of crypt() that doesn't grok MD5 passwords. In those cases the OS
library providing crypt() must be referenced *before* OpenSSL's libcrypto.
In the particular case of OSes that have crypt() in libcrypt, specifying
-lcrypt via configure's --with-libs option has worked for me.

--Per Hedeland
per@hedeland.org