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: FW: Logging logins only?

Subject: Re: FW: Logging logins only?
Date: Wed, 10 Nov 2004 05:10:06 -0600
Ryan Kish wrote:

Maybe someone here has a suggestion short of that? Or maybe I have
missed some trick somewhere?



You may want to consider using syslog-ng as your log servers syslog deamon:(http://www.balabit.com/products/syslog_ng/). You may be able to set up a string of filters that will allow you to capture only the information your interested in.

Cheers,
Ryan




Thanks everyone for the quick replies.

Of course I know how to use grep to filter the logs for easy reading, but its too late then. I need a way of filtering them before or at the syslog server (before they are sent to the line printer.)

Syslog-ng looks like it might do exactly what I need. I don't like having to fix something thats not really broken, but I need the added functionality so I guess I will give that a try.

Cheers all!

Blair

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