From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, kevin.boyce@ngc.com
Subject: Re: Audit Dispatcher
Date: Mon, 25 Feb 2008 16:05:30 -0500 [thread overview]
Message-ID: <200802251605.30863.sgrubb@redhat.com> (raw)
In-Reply-To: <1203972975.5209.24.camel@pc070168.northgrum.com>
On Monday 25 February 2008 15:56:15 Kevin Boyce wrote:
> Is there any recommended audit dispatcher for the the RHEL audit daemon?
In the 5.2 update we are switching from the python based dispatcher (audit
1.4.1 era) to an improved C based multi-threaded dispatcher (roughly current
with 1.6.8's). I will probably be backporting the same dispatcher to RHEL4.7.
There very well could be other 3rd party dispatchers out there, but I don't
know where you would find them and I have not tested them. Also, the
dispatcher needs SE Linux policy updates since auditd_t is a confined domain.
So, a third party dispatcher has that hurdle to jump over, too.
-Steve
prev parent reply other threads:[~2008-02-25 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 20:56 Audit Dispatcher Kevin Boyce
2008-02-25 21:05 ` Steve Grubb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802251605.30863.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=kevin.boyce@ngc.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox