public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: zhangxiliang <zhangxiliang@cn.fujitsu.com>
Cc: linux-audit@redhat.com
Subject: Re: A question about the directory watch in audit_tree.c in kernel
Date: Wed, 21 May 2008 11:03:34 -0400	[thread overview]
Message-ID: <200805211103.34938.sgrubb@redhat.com> (raw)
In-Reply-To: <002501c8bae4$b3491480$2e8da70a@fnste3fa5f55c4>

On Tuesday 20 May 2008 21:47:59 zhangxiliang wrote:
> Sorry, I think my idea may be not express correctly. A example as follows:
> 1, mkdir test
> 2, touch test.c
> 3, auditctl -w /home/test -k 11
> 4, auditctl -w /home/test.c -k 11

And then what did you do to create these records?


> My question is why no information will be output by kernel hook funtion?

What is missing? I can't tell what commands you run and what you expected to 
be output by the kernel.


> Correct me if I am wrong, I think when watch a directory, kernel-audit can
> also supply more information by kernel hook funtion

What other information do you need?

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

  reply	other threads:[~2008-05-21 15:03 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 [this message]
2008-05-22 12:28       ` LC Bruzenak
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=200805211103.34938.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=zhangxiliang@cn.fujitsu.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