From: Steve Grubb <sgrubb@redhat.com>
To: Linux-audit@redhat.com, Andreas Hasenack <andreas@canonical.com>
Subject: Re: -a never,exit still being logged
Date: Thu, 19 Nov 2020 14:54:20 -0500 [thread overview]
Message-ID: <7875988.NyiUUSuA9g@x2> (raw)
In-Reply-To: <CANYNYEE1T5y9injWUjx=X300nC_GYRVW6P8WS+DLq3e1W=diLA@mail.gmail.com>
On Thursday, November 19, 2020 1:59:58 PM EST Andreas Hasenack wrote:
> Hi,
>
> On Thu, Nov 19, 2020 at 3:52 PM Steve Grubb <sgrubb@redhat.com> wrote:
> > On Thursday, November 19, 2020 1:43:34 PM EST Andreas Hasenack wrote:
> > > Why is it being logged, given that it matches the second (and last)
> > > rule I
> > > have?
> >
> > These two events are considered kernel configuration changes. Which means
> > that they do not originate via the SYSCALL rule engine. The -a
> > never,exit technique works only when the event is generated as a result
> > of other SYSCALL rules. Normally you would place that higher up so it
> > matches first.
> >
> > In this case, what you would want to do is suppress it using the exclude
> > filter:
> >
> > -a always,exclude -F msgtype=NETFILTER_CFG
> >
> > That should fix it.
>
> I see, and I can still add auid=-1 to that one, right? Just not the exe
> filter?
You can add the -F auid=-1 if you want to.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2020-11-19 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 18:43 -a never,exit still being logged Andreas Hasenack
2020-11-19 18:52 ` Steve Grubb
2020-11-19 18:59 ` Andreas Hasenack
2020-11-19 19:54 ` 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=7875988.NyiUUSuA9g@x2 \
--to=sgrubb@redhat.com \
--cc=Linux-audit@redhat.com \
--cc=andreas@canonical.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