From: Stephen Smalley <sds@tycho.nsa.gov>
To: "Clarkson, Mike R (US SSA)" <mike.clarkson@baesystems.com>
Cc: selinux@tycho.nsa.gov, Eric Paris <eparis@parisplace.org>,
James Morris <jmorris@namei.org>
Subject: Re: filesystem mount AVC denial
Date: Mon, 02 Feb 2009 09:04:13 -0500 [thread overview]
Message-ID: <1233583453.3826.4.camel@localhost.localdomain> (raw)
In-Reply-To: <7b4dai$ejec6@dmzms99901.na.baesystems.com>
On Fri, 2009-01-30 at 15:45 -0800, Clarkson, Mike R (US SSA) wrote:
> I got the following AVC denial in the audit logs and I'm wondering what
> would cause this:
>
> type=AVC msg=audit(1232734163.528:997720):avc: denied { mount } for
> pid=28016 comm="find" name="/" dev=0:1c ino=0
> scontext=root:staff_r:libstart_t:s0-s4:c0.c255
> tcontext=system_u:object_r:nfs_t:s0 tclass=filesystem
>
> The program running in the libstart_t domain is using the "find" cmd,
> and find is requiring the "mount" permission. Could this be caused by
> "find" traversing into an automounted (NFS) directory? But in that case
> I would expect the automount daemon, which is running in the automount_t
> domain, to do the mounting.
Could be a nfs submount, triggered upon traversing the boundary?
--
Stephen Smalley
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2009-02-02 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 23:45 filesystem mount AVC denial Clarkson, Mike R (US SSA)
2009-02-02 14:04 ` Stephen Smalley [this message]
2009-02-02 19:02 ` Daniel J Walsh
2009-02-03 13:41 ` Stephen Smalley
2009-02-04 0:18 ` James Morris
2009-02-04 16:12 ` Stephen Smalley
2009-02-02 19:07 ` Daniel J Walsh
2009-02-02 19:55 ` Daniel J Walsh
-- strict thread matches above, loose matches on Subject: below --
2009-02-03 16:51 Clarkson, Mike R (US SSA)
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=1233583453.3826.4.camel@localhost.localdomain \
--to=sds@tycho.nsa.gov \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=mike.clarkson@baesystems.com \
--cc=selinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.