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: Alternative logging destination for sshd

Subject: Re: Alternative logging destination for sshd
Date: Fri, 20 Jan 2006 13:36:54 +1100
On Thu, Jan 19, 2006 at 02:43:04PM +0100, Tob_Sch@gmx.de wrote:
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?

You would need to modify the code or provide replacements for
openlog/syslog/closelog.

Most syslogds will write to a named pipe if you configure them to do
so, though.  Would that serve your purpose?

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