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. |

| Subject: | Re: Alternative logging destination for sshd |
|---|---|
| Date: | Thu, 19 Jan 2006 15:30:48 +0100 |
Tob_Sch@gmx.de a écrit :
Hi, we are using OpenSSH 4.2p1. Is it possible (with the help of documented or undocumented sshd_config parameters, or by changing some header file entries in the source) to force sshd to log to a named pipe instead to syslog?
Why not use syslog-ng with a filter? This way you could do whatever you want with your ssh logs even send them to a postgreSQL database and analyse them in realtime with help of some triggers. my 0.02€ -- Christophe Garault
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: AllowUsers issue, Darren Tucker |
|---|---|
| Next by Date: | Re: AllowUsers issue, Darren Tucker |
| Previous by Thread: | Alternative logging destination for sshd, Tob_Sch |
| Next by Thread: | Re: Alternative logging destination for sshd, Darren Tucker |
| Indexes: | [Date] [Thread] [Top] [All Lists] |