From: James Morris <jmorris@namei.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@redhat.com>,
David Quigley <dpquigl@tycho.nsa.gov>,
Chris Wright <chrisw@sous-sol.org>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 2/3] SELinux: add security_task_movememory calls to mm code
Date: Thu, 22 Jun 2006 15:10:24 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606221504370.21897@d.namei> (raw)
In-Reply-To: <20060622123102.GF27074@sergelap.austin.ibm.com>
On Thu, 22 Jun 2006, Serge E. Hallyn wrote:
> sorry if I'm being dense - what is actually being protected against
> here? The only thing I can think of is one process causing performance
> degradation to another by moving it's memory further from it's cpu on a
> NUMA machine.
This is a privileged operation, which currently relies only on uid (i.e.
traditional Unix DAC), and capability checking.
SELinux introduces Mandatory Access Control (MAC) based upon all
security-relevant attributes of tasks and objects, not just uid/capability
checks. Theoretically, all processes could run with euid==0 under SELinux
(in fact, Russell Coker's 'play box' does something similar by giving out
the root password to everyone, although SELinux is designed to complement
DAC, not replace it).
Any privileged operations with DAC controls also need corresponding MAC
controls, which is what this patch implements.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2006-06-22 19:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 19:20 [PATCH 1/3] SELinux: Add security hook definitions for setmempolicy James Morris
2006-06-21 19:23 ` [PATCH 2/3] SELinux: add security_task_setmempolicy hooks to mm code James Morris
2006-06-21 19:33 ` Christoph Lameter
2006-06-21 19:51 ` James Morris
2006-06-21 20:07 ` Christoph Lameter
2006-06-21 20:47 ` James Morris
2006-06-21 19:26 ` [PATCH 3/3] SELinux: Add sockcreate node to procattr API James Morris
2006-06-21 21:33 ` [PATCH 0/3] SELinux: movememory & sockcreate updates for -mm James Morris
2006-06-21 21:34 ` [PATCH 1/3] SELinux: add task_movememory hook James Morris
2006-06-22 21:53 ` Chris Wright
2006-06-21 21:36 ` [PATCH 2/3] SELinux: add security_task_movememory calls to mm code James Morris
2006-06-21 21:43 ` Christoph Lameter
2006-06-21 21:54 ` James Morris
2006-06-22 12:31 ` Serge E. Hallyn
2006-06-22 14:55 ` Christoph Lameter
2006-06-22 19:10 ` James Morris [this message]
2006-06-22 19:21 ` Chris Wright
2006-06-22 21:53 ` Chris Wright
2006-06-21 21:37 ` [PATCH 3/3] SELinux: Add sockcreate node to procattr API James Morris
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=Pine.LNX.4.64.0606221504370.21897@d.namei \
--to=jmorris@namei.org \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=clameter@sgi.com \
--cc=dpquigl@tycho.nsa.gov \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=serue@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®