From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: auditctl usage for filter lists: "user" , "watch" and "exclude"
Date: Thu, 18 May 2006 11:55:15 -0400
Message-ID: <200605181155.15157.sgrubb@redhat.com>
References: <446C8915.20606@us.ibm.com> <446C8BCC.1020002@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <446C8BCC.1020002@us.ibm.com>
Content-Disposition: inline
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: linux-audit@redhat.com
List-Id: linux-audit@redhat.com

On Thursday 18 May 2006 10:59, Michael C Thompson wrote:
> Question, is it intended for:
> auditctl -a exclude,always -F msgtype=3DCONFIG_CHANGE
> =A0 =A0and
> auditctl -a exclude,never -F msgtype=3DCONFIG_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=
=20
match "wins" though, so the second rule would not apply. I can see that y=
ou=20
may want to do something like this:

-a exclude,never -F msgtype=3DDAEMON_END
-a exclude,always -F 'msgtype>=3DDAEMON_START' -F 'msgtype<=3DDAEMON_ROTA=
TE'

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

-Steve