public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: -a task,always audits everything
Date: Wed, 21 Feb 2007 15:53:40 -0500	[thread overview]
Message-ID: <200702211553.40324.sgrubb@redhat.com> (raw)
In-Reply-To: <1172056466.3970.17.camel@localhost.localdomain>

On Wednesday 21 February 2007 06:14:26 Matthew Booth wrote:
> I added the following to audit.rules in RHEL4 U4 x86_64:
>
> -a task,always
>
> I expected this to have a similar effect to auditing the fork, vfork and
> clone system calls.

Task auditing and syscall auditing are a little different. Task filters would 
most likely be used a field (-F) option. What the above is doing is marking 
each task auditable as its created.

> However, it seems to either audit everything itself, 

As given, I think so. What happens is that with no fields, the 
audit_filter_rules() function in the kernel avoids the switch case and winds 
up in another branch which is for situations like:

auditctl -a always,exit -s open

In that case, you would want to audit any call to open. So, what happens is 
each task is marked auditable as its created since there are no field 
qualifiers to discriminate with.

> or cause all the filtering to be removed from my other audit rules (which
> audit pretty much everything). 

Audit is a first match wins system.

> Is this expected behaviour, or a bug?

I think this is expected.

-Steve

      reply	other threads:[~2007-02-21 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 11:14 -a task,always audits everything Matthew Booth
2007-02-21 20:53 ` 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=200702211553.40324.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