public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: A question about the directory watch in audit_tree.c in kernel
Date: Thu, 22 May 2008 07:28:13 -0500	[thread overview]
Message-ID: <1211459293.6597.9.camel@homeserver> (raw)
In-Reply-To: <200805211103.34938.sgrubb@redhat.com>


On Wed, 2008-05-21 at 11:03 -0400, Steve Grubb wrote:
...
> 
> Also, note that -w rules are legacy for compatibility with RHEL4 kernel. They 
> are used to express simple ideas like watch this file or directory subtree. 
> If you want tight control over what you are auditing, you should use the 
> syscall audit format where you can express more details about what you wanted 
> to trigger on. IOW, you can express that you want changes to a directory 
> itself rather than the files in the directory.
> 
> -Steve

Steve, do any of the syscall directory watches recursively audit to the
bottom of a given directory tree?

I had kept many "-w" fields in place b/c the man page says they do not
impact performance based on the number of rules, and I wanted the full
subtree covered. 
Should look to changing these watches to specific syscall watches in
order to not get "legacied out" at some point?

Thx,
LCB.

-- 
LC (Lenny) Bruzenak
lenny@magitekltd.com

  reply	other threads:[~2008-05-22 12:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20  1:11 A question about the directory watch in audit_tree.c in kernel zhangxiliang
2008-05-20 12:06 ` Kevin Boyce
2008-05-20 12:41   ` Steve Grubb
2008-05-21  1:47   ` zhangxiliang
2008-05-21 15:03     ` Steve Grubb
2008-05-22 12:28       ` LC Bruzenak [this message]
2008-05-22 13:09         ` 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=1211459293.6597.9.camel@homeserver \
    --to=lenny@magitekltd.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@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