Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

PAM and password authentication

Subject: PAM and password authentication
Date: Fri, 13 Aug 2004 12:15:32 -0400 (EDT)
I am trying to get password authentication to go via the PAM stack on
3.8.1p1-4 (that is, the version from Debian sarge/testing), running under
Debian testing.

I have added the line "UsePAM yes" and left password authentication
enabled in sshd_config. When someone logs in via keyboard-interactive, the
authentication goes via PAM. When they log in using the password
authentication, ssh goes straight to the password file. Disabling
privelege separation does nothing to change this behaviour.

This is an issue for us because the windows ssh commercial client does not
do keyboard-interactive authentication by default and I need to make
things as easy as possible for the users.

Does PAM only work via keyboard-interactive?


<Prev in Thread] Current Thread [Next in Thread>