On Mon, 14 Jun 1999, Wojtek Pilorz wrote:
> Subject: Re: MD5 passwords
>
> On 12 Jun 1999, Niels [ISO-8859-1] M�ller wrote:
>
[...]
> >
> > I discovered that when reading the glibc documentation. However, it
> > still doesn't work. Say that I have the password "gazonk" on this
> > system. I.e. that's a password that I can use to login successfully.
> > Then look at the line in /etc/passwd, which contains the encrypted
> > password
> >
> > $1$salt$ABCX7Qxx
> >
> > I wrote a testprograms that calls glibc:s crypt. If I invoke it with
> > the salt taken from the passwd file, and my working password, the
> > result does _not_ match the line in /etc/passwd. It appears that pam
> > and glibc are not compatible. Although both use the same magic cookie
> My tests seem to show that they indeed are compatible.
> Please look at the attached file.
> To compile it just run
> cat how_compiled2.txt | sh
>
> The program is a slightly modified testpass.c.texi from
> glibc-crypt-2.1.tar.gz (which is included in glibc-2.1.1-7.src.rpm on
> RedHat 6.0 source CD)
>
> I have compiled and run it on RedHat 6.0 and RedHat 5.2 (updated to run
> 2.2.x kernel), feeding it output from /etc/shadow password field,
> generated through PAM on RedHat 4.2 and on RedHat 5.2.
OK, to be sure I have also tried previously attached program using
/etc/shadow entries generated on RedHat Linux 6.0 (with pam-0.66-18 installed);
And again it is OK. Am I missing something?
>
> The session looked as follows:
> [wpilorz@RHL52 test]$ ./testpass2
> Give encoded password string :$1$lVLqz8ae$8QdL3o8gQhpFZ8ih82CVa/
> Password:
> Access granted.
> Encoded result was '$1$lVLqz8ae$8QdL3o8gQhpFZ8ih82CVa/'
> $
>
> The password was "test 001" (without quotes).
>
[...]
Best regards,
Wojtek
