--EY/WZ/HvNxOox07X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 03, 2002 at 11:10:01AM -0700, light storm wrote: > First of all thanks for anytime you put in my problem, really > appreciate all the help cause i just don't see it :( > I'll paste here the additional information which might help solve this: > (note: openssh was compiled with pam support and md5 support) > sshd pam file for openssh in /etc/pam.d/ Have you checked your log files for anything that might tell you which PAM module is failing and why? pam_unix, at least, logs a fair amount of information to the syslog 'auth' facility, and more information is=20 available if you add the 'debug' flag to the module arguments auth required /lib/security/pam_unix.so debug Your openssh debug output indicates that PAM is being invoked, and your=20 PAM config file looks reasonable from what I can tell; so looking at=20 logs would be the next step. > #%PAM-1.0 > auth required /lib/security/pam_unix.so # set_secrpc > auth required /lib/security/pam_nologin.so > auth required /lib/security/pam_env.so > account required /lib/security/pam_unix.so > password required /lib/security/pam_pwcheck.so md5 BTW, does pam_pwcheck.so really support this 'md5' argument? As a quick experiment, you might try removing it to see if that changes openssh's behavior -- though the effect on the authentication process of a misconfigured password module should really be minimal. Steve Langasek postmodern programmer --EY/WZ/HvNxOox07X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE81pNcKN6ufymYLloRAsbRAJ9lz57C+OSK/Ce+6SKAA3cvM/1W4gCgqGwe x0lGxmAyDge9lu2Hk30PpGE= =N6WS -----END PGP SIGNATURE----- --EY/WZ/HvNxOox07X--
