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]

RE: using ssh for login authifcation

Subject: RE: using ssh for login authifcation
Date: Wed, 12 Apr 2006 11:10:36 -0700
It does indeed sound like what you have isn't so much an SSH issue as it is
a PAM configuration one.  It sounds like you may want to just disable the
use of PAM in your SSH configuration altogether.

Without knowing anything specific about your configuration, I don't know if
that's a valid option for you, but it should give you the behavior you want.

-----Original Message-----
From: Keld Jørn Simonsen [mailto:keld@dkuug.dk] 
Sent: Wednesday, April 12, 2006 9:24 AM
To: secureshell@securityfocus.com
Subject: using ssh for login authifcation

I use ssh all the time and I am irritated that I need to first login via my
passwd and then give my passphrase. I thought why not just give the
passphrase, as I do when I do a remote login via ssh.

I got the message from the list moderator that this may be irrelevant here -
but IMHO it is related to ssh. Anyway he pointed me to PAM, and indeed I
found a module pam_ssh.so that should fullfill my wishes.

So my question is: is pam_ssh the way forward?

[snip]



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