From: "Camilo Y. Campo" <camilo@br.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linux-audit@redhat.com
Subject: Re: audit in /selinux directory
Date: Wed, 14 Mar 2007 01:10:47 -0300 [thread overview]
Message-ID: <1173845448.5936.6.camel@cyc> (raw)
In-Reply-To: <1173475552.3241.148.camel@moss-spartans.epoch.ncsc.mil>
On Fri, 2007-03-09 at 16:25 -0500, Stephen Smalley wrote:
> On Fri, 2007-03-09 at 16:17 -0500, Stephen Smalley wrote:
> > On Fri, 2007-03-09 at 16:13 -0500, Stephen Smalley wrote:
> > > On Fri, 2007-03-09 at 15:23 -0500, Steve Grubb wrote:
> > > > On Friday 09 March 2007 14:31, Camilo Y. Campo wrote:
> > > > > The cat command failed and audit is saying "success". A bit strange for
> > > > > me. Could anybody clarify this point for me, please?
> > > >
> > > > It works correctly for me:
> > > >
> > > > fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
> > > > open("/selinux/disable", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)
> > >
> > > You got EACCES rather than EINVAL, so your test didn't reach the same
> > > point in the code path. Try it as root (and with appropriate SELinux
> > > role/domain if under -strict or -mls).
> >
> > I tried it, and the open succeeds, but the read fails with -EINVAL
> > because the underlying pseudo file doesn't implement a read method at
> > all for that node. So the audit is only capturing the open, which was
> > successful.
>
> And since one has to be root to open it at all, and root has
> dac_read_search, you can bypass the DAC mode on it at open time.
> So...not a bug?
For me this seems a bug... if I can't audit a denied access in a watched
file...
Camilo Y. Campo
prev parent reply other threads:[~2007-03-14 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 19:31 audit in /selinux directory Camilo Y. Campo
2007-03-09 20:23 ` Steve Grubb
2007-03-09 21:13 ` Stephen Smalley
2007-03-09 21:17 ` Stephen Smalley
2007-03-09 21:25 ` Stephen Smalley
2007-03-14 4:10 ` Camilo Y. Campo [this message]
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=1173845448.5936.6.camel@cyc \
--to=camilo@br.ibm.com \
--cc=linux-audit@redhat.com \
--cc=sds@tycho.nsa.gov \
/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