From: Arjan van de Ven <arjan@infradead.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov,
sds@tycho.nsa.gov, jmorris@namei.org, spender@grsecurity.net,
dwalsh@redhat.com, cl@linux-foundation.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: mmap_min_addr and your local LSM (ok, just SELinux)
Date: Mon, 20 Jul 2009 20:48:48 -0700 [thread overview]
Message-ID: <20090720204848.5f37c92a@infradead.org> (raw)
In-Reply-To: <1248132223.2654.278.camel@localhost>
On Mon, 20 Jul 2009 19:23:43 -0400
Eric Paris <eparis@redhat.com> wrote:
>
> Does anyone see a better way to let users continue to be users while
> protecting most people? Yes SELinux is stronger in some areas than
> without confining the ability to map the 0 page, but as has be rightly
> pointed out it's foolish an broken that SELinux can weaken any
> protections.
one option is to allow the page to be mapped, but only as
non-executable... in DOS that memory isn't where code lives anyway...
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-07-21 3:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 23:23 mmap_min_addr and your local LSM (ok, just SELinux) Eric Paris
2009-07-21 0:14 ` Christopher Pardy
2009-07-21 13:41 ` Daniel J Walsh
2009-07-21 3:45 ` James Morris
2009-07-21 14:44 ` James Carter
2009-07-22 10:06 ` James Morris
2009-07-28 0:19 ` Alan Cox
2009-07-28 3:28 ` Kyle Moffett
2009-07-28 9:21 ` Andi Kleen
2009-07-28 10:00 ` Alan Cox
2009-07-28 11:21 ` Andi Kleen
2009-07-28 13:35 ` Brad Spengler
2009-07-28 14:48 ` Andi Kleen
2009-07-28 15:56 ` Kees Cook
2009-07-28 16:23 ` Andi Kleen
2009-07-21 3:48 ` Arjan van de Ven [this message]
2009-07-21 11:51 ` Brad Spengler
2009-07-21 4:13 ` Kyle McMartin
2009-07-21 11:31 ` Arnd Bergmann
2009-07-30 9:06 ` Pavel Machek
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=20090720204848.5f37c92a@infradead.org \
--to=arjan@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cl@linux-foundation.org \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=spender@grsecurity.net \
/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