Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Monitoring events
Date: Thu, 8 Jun 2006 11:23:21 -0400	[thread overview]
Message-ID: <200606081123.21710.sgrubb@redhat.com> (raw)
In-Reply-To: <44883AD8.9070307@ornl.gov>

On Thursday 08 June 2006 10:57, Steve wrote:
> So, assuming I installed RHEL4, would this "key tag" allow all events to
> be tied to rules, or just the file watch events?

There has been some talk about adding the "key" to LSPP kernels. So this might 
be available eventually. (You are testing against a kernel that is under 
development and not feature complate.)

RHEL4 on the otherhand has an older audit system. I have not backported the 
audit dispatcher interface to the 1.0.X series. It shouldn't be difficult and 
might be something I do for 1.0.15.

-Steve

      reply	other threads:[~2006-06-08 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 13:55 Monitoring events Steve
2006-06-08 14:04 ` Steve Grubb
2006-06-08 14:22   ` Steve
2006-06-08 14:39     ` Steve Grubb
2006-06-08 14:57       ` Steve
2006-06-08 15:23         ` 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=200606081123.21710.sgrubb@redhat.com \
    --to=sgrubb@redhat.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