From: Linda Knippers <linda.knippers@hp.com>
To: Klaus Weidner <klaus@atsec.com>
Cc: linux-audit@redhat.com
Subject: Re: watching files in selinuxfs
Date: Wed, 27 Sep 2006 18:18:45 -0400 [thread overview]
Message-ID: <451AF8C5.4070806@hp.com> (raw)
In-Reply-To: <20060927221131.GA10199@w-m-p.com>
Klaus Weidner wrote:
> On Wed, Sep 27, 2006 at 05:46:52PM -0400, Linda Knippers wrote:
>
>>Debora Velarde wrote:
>>
>>># auditctl -a exit,always -S open -F inode=4
>>># auditctl -l
>>>LIST_RULES: exit,always inode=4 (0x4) syscall=open
>>
>>I wonder what this is actually doing. An inode number without
>>a file system isn't very interesting. Should this rule even
>>be accepted?
>
>
> Well, probably this is telling the audit system to audit access to all
> inodes with the number 4 on any filesystem, and if that's not what you
> want you need to be more specific...
That's exactly what its doing. Debora verified she's getting the audit
record she's looking for and I verified that you'll also get audit records
for any inode 4, at least on my system.
>
> Given the Unix philosophy of allowing admins to shoot themselves in the
> foot, would a warning be appropriate?
I would think so. I'm not exactly sure how you'd specify the file system
you want. Is the major/minor pair?
-- ljk
next prev parent reply other threads:[~2006-09-27 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 21:26 watching files in selinuxfs Debora Velarde
2006-09-27 21:46 ` Linda Knippers
2006-09-27 22:11 ` Klaus Weidner
2006-09-27 22:18 ` Linda Knippers [this message]
2006-09-28 1:59 ` Valdis.Kletnieks
2006-09-28 15:33 ` Casey Schaufler
2006-09-28 13:34 ` Stephen Smalley
2006-09-28 18:39 ` Debora Velarde
2006-09-28 20:33 ` Steve Grubb
2006-09-28 20:42 ` Stephen Smalley
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=451AF8C5.4070806@hp.com \
--to=linda.knippers@hp.com \
--cc=klaus@atsec.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