All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael C Thompson <thompsmc@us.ibm.com>
To: Michael C Thompson <thompsmc@us.ibm.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: auditctl usage for filter lists: "user" , "watch" and "exclude"
Date: Thu, 18 May 2006 09:59:24 -0500	[thread overview]
Message-ID: <446C8BCC.1020002@us.ibm.com> (raw)
In-Reply-To: <446C8915.20606@us.ibm.com>

Michael C Thompson wrote:
> Hey all,
> 
> I'm trying to understand better the user, watch and exclude auditctl 
> filter lists. I believe I have a reasonable understanding of exclude 
> from some examples Steve gave (see below), but I have very little idea 
> of how user is meant to be used, and none about watch.
> 
> Any enlightenment will be helpful.
> 
> For the exclude list,
> 
> exclude,always -F msgtype=SYSCALL
> 
> seems to be the only valid structure, where msgtype can be any value 
> (XXX) for the type in the audit.log? (where the 1st field in the audit 
> log is type=XXX)
> 
> Are there more filters that apply? (and does it have any meaning without 
> a filter?)

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?

Mike

  reply	other threads:[~2006-05-18 14:59 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 [this message]
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
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=446C8BCC.1020002@us.ibm.com \
    --to=thompsmc@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.