From: Arnd Bergmann <arnd@arndb.de>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Eric Paris <eparis@redhat.com>,
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, arjan@infradead.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: mmap_min_addr and your local LSM (ok, just SELinux)
Date: Tue, 21 Jul 2009 13:31:50 +0200 [thread overview]
Message-ID: <200907211331.50196.arnd@arndb.de> (raw)
In-Reply-To: <20090721041311.GE11051@bombadil.infradead.org>
On Tuesday 21 July 2009, Kyle McMartin wrote:
>
> Why do we not add a personality flag for this? With that, at least you
> could require a harmless setuid wrapper for wine that just set the
> personality bits and dropped root.
I thought the MMAP_PAGE_ZERO personality bit was exactly what Brad
was using in his demonstration. We don't need to define a new bit,
just use the one that's there ;-).
Then again, setting personality flags does not require root permissions
normally, so it's not an extremely strong protection, unless you also
start requiring CAP_SYS_RAWIO for setting MMAP_PAGE_ZERO.
Arnd <><
next prev parent reply other threads:[~2009-07-21 11:32 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
2009-07-21 11:51 ` Brad Spengler
2009-07-21 4:13 ` Kyle McMartin
2009-07-21 11:31 ` Arnd Bergmann [this message]
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=200907211331.50196.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=cl@linux-foundation.org \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=kyle@mcmartin.ca \
--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