From: Paul Moore <paul.moore@hp.com>
To: Michael C Thompson <thompsmc@us.ibm.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: do SELinux write/read permission checks exist?
Date: Wed, 22 Nov 2006 09:51:40 -0500 [thread overview]
Message-ID: <456463FC.803@hp.com> (raw)
In-Reply-To: <4564557F.7030009@us.ibm.com>
Michael C Thompson wrote:
> So, I've managed to loose track of this in my mind, but does SELinux do
> permission checks for sys_read and sys_write?
Take a look at vfs_write() and vfs_read() and you will see that they both call
the LSM security_file_permission() hook which under SELinux is defined by the
selinux_file_permission in security/selinux/hooks.c.
--
paul moore
linux security @ hp
--
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.
prev parent reply other threads:[~2006-11-22 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 13:49 do SELinux write/read permission checks exist? Michael C Thompson
2006-11-22 14:36 ` Stephen Smalley
2006-11-22 14:51 ` Paul Moore [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=456463FC.803@hp.com \
--to=paul.moore@hp.com \
--cc=selinux@tycho.nsa.gov \
--cc=thompsmc@us.ibm.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 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.