Wally, I think your problem is related to either configure options and
sshd_config options.
In 2.9 there is an option in sshd_config called:
PAMAuthenticationViaKdbInt
This needs to be yes and
PasswordAuthentication
needs to be no. The reason is PasswordAuthentication seems to take precedence
over PAM. At least it did on my setup. PasswordAuthentication goes directly to
the password file via getpwent/getspent directly.
So, if you leave password authentication enabled, it will not use PAM. Thus,
you will need to make sure you built sshd with --with-md5-passwords so it can
read and interpret the passwords in the Linux shadow password file. If this
option isn't given it expects crypt style passwords which won't match.
Hope this helps.
--Dave
>Date: Mon, 16 Jul 2001 20:14:53 -0700
>From: "Auteria Wally Winzer Jr." <[EMAIL PROTECTED]>
>X-Accept-Language: en
>MIME-Version: 1.0
>To: [EMAIL PROTECTED]
>Subject: REPOST #3: Openssh 2.9p2 login authentication problem(s) on Mandrake
7.0
>X-OriginalArrivalTime: 17 Jul 2001 03:14:45.0494 (UTC)
FILETIME=[A1176160:01C10E6E]
>
>I had previous problems w/ 2.5.2p2 using password authentication on
>Mandrake-7.0. I type in my password, and it claims it's invalid, yet I
>log in via telnet and my password works fine. I enable the --with-pam
>option within configure. I grabbed the /etc/pam.d/ssh file from my
>RedHat system and transfered it onto /etc/pam.d Here's what my sshd
>file looks like:
>
>#%PAM-1.0
>auth required /lib/security/pam_pwdb.so shadow
>auth required /lib/security/pam_nologin.so
>account required /lib/security/pam_pwdb.so
>password required /lib/security/pam_cracklib.so
>password required /lib/security/pam_pwdb.so shadow nullok use_authtok
>session required /lib/security/pam_pwdb.so
>
>No errors within my syslog (pam authentication, etc.).
--
David Knight French
Black Mountain Computer Consulting
Voice: (858)573-2959
Email: [EMAIL PROTECTED]
