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: Auditing SSH logs

Subject: Re: Auditing SSH logs
Date: Tue, 05 Jun 2007 08:02:29 +1000
Flavio Junior wrote:
Hi folks, good morning/afternoon/evening ;)

I'll try explain my doubt, but sorry for my english..

Can someone tell me if has a way to do SSHD log shows me "which" key
has been accepted when logged as root ?

Example:
"May 31 15:15:17 lazlo sshd[12583]: Accepted publickey for root from
192.168.4.192 port 1835 ssh2"

But ... which key has been accepted ? how can i audit something like
it, if i have more than a single key on authorized_keys for root

Set "LogLevel verbose" in sshd_config and you'll get the key fingerprint logged in syslog too ("Found matching RSA key: XX:XX..")


--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

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