OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: [RFC] environment sanitisation wrapper
From: Sean Hunter (seanuncarved.com)
Date: Wed May 31 2000 - 13:38:57 CDT

No it isn't. My method prints out to a file handle (stderr). You can
run the thing in a shell that pipes those messages into logger or
splogger or something so they end up in syslog, or you can use
multilog or put them in a static file, or whatever.

Your method uses syslog.h etc. That means the method is set.

Sean

On Wed, May 31, 2000 at 11:17:37AM -0700, K2 wrote:
>
> I dont know how this got into a conversation about what syslog is
> better, to the programmer they all look the same, and based on the fact
> we were talking about how to code an alert for an intrusion attempt,
> syslog() works fine, whatever syslogd you use is totally up to the admin
> not the programmer...
>
> K2
>
> On Wed, 31 May 2000, Kurt Seifried wrote:
>
> > > Thanks very much for this. Any recommendations out of this list?
> >
> > Depends on your needs. For secure logging (i.e. encrypted and signed)
> > secure-syslog is prolly yer best bet, followed by nsyslog, for flexibility
> > syslog-ng is great (filter based on messages). You might consider a combo,
> > i.e. one set of logging, secured, ssl, signed, etc to a secure host (for use
> > as evidence in a prosecution), and another to a syslog-ng host used for
> > moinitoring/etc.
> >
> > > Sean
> >
> > -Kurt
> >
>