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: auditctl usage for filter lists: "user" , "watch" and "exclude"
Date: Thu, 18 May 2006 11:55:15 -0400	[thread overview]
Message-ID: <200605181155.15157.sgrubb@redhat.com> (raw)
In-Reply-To: <446C8BCC.1020002@us.ibm.com>

On Thursday 18 May 2006 10:59, Michael C Thompson wrote:
> Question, is it intended for:
> auditctl -a exclude,always -F msgtype=CONFIG_CHANGE
>    and
> auditctl -a exclude,never -F msgtype=CONFIG_CHANGE
>
> (being active at different times) to both block the CONFIG_CHANGE
> messages? I would assume that exclude,never to _not_ block messages of
> that type?

I can't see a reason to have both for the same msgtype. The first rule to 
match "wins" though, so the second rule would not apply. I can see that you 
may want to do something like this:

-a exclude,never -F msgtype=DAEMON_END
-a exclude,always -F 'msgtype>=DAEMON_START' -F 'msgtype<=DAEMON_ROTATE'

Together, this means exclude all messages in the DAEMON_* range except the 
DAEMON_END message.

-Steve

  parent reply	other threads:[~2006-05-18 15:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 14:47 auditctl usage for filter lists: "user" , "watch" and "exclude" Michael C Thompson
2006-05-18 14:59 ` Michael C Thompson
2006-05-18 15:41   ` Michael C Thompson
2006-05-18 15:58     ` Steve Grubb
2006-05-18 16:04       ` Michael C Thompson
2006-05-18 16:16         ` Steve Grubb
2006-05-18 19:01           ` Michael C Thompson
2006-05-18 19:29             ` Steve Grubb
2006-05-18 15:55   ` Steve Grubb [this message]
2006-05-18 15:58     ` Michael C Thompson
2006-05-18 16:13       ` Steve Grubb
2006-05-18 15:50 ` Steve Grubb

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=200605181155.15157.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