Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Knippers <linda.knippers@hp.com>
To: Debora Velarde <dvelarde@us.ibm.com>
Cc: linux-audit@redhat.com
Subject: Re: watching files in selinuxfs
Date: Wed, 27 Sep 2006 17:46:52 -0400	[thread overview]
Message-ID: <451AF14C.9080908@hp.com> (raw)
In-Reply-To: <OF86C13FA9.9583DDF2-ON872571F6.00745C68-882571F6.0075C970@us.ibm.com>

Debora Velarde wrote:
> When in enforcing mode, I am only able to audit files in selinuxfs by 
> inode, not by path.    I am running as auditadm_r.
> 
> /* Try adding audit rule with -F path */
> # auditctl -a exit,always -S open -F path=/selinux/enforce
> Error sending add rule request (Permission denied)
> 
> # auditctl -l
> No rules
> 
> /* Try adding audit rule with -w path syntax */
> # auditctl -w /selinux/enforce
> Error sending add rule request (Permission denied)
> 
> /* Try adding audit rule with -F inode */
> # ls -i /selinux/enforce
> 4 /selinux/enforce
> 
> # 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?

> 
> Since it is possible to audit the files, this might only require a 
> documentation change.  Perhaps adding a comment to the auditctl man page 
> would be sufficient?
> 
> -debbie
> 
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2006-09-27 21:47 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 [this message]
2006-09-27 22:11   ` Klaus Weidner
2006-09-27 22:18     ` Linda Knippers
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=451AF14C.9080908@hp.com \
    --to=linda.knippers@hp.com \
    --cc=dvelarde@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox