From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org, sds@tycho.nsa.gov,
jmorris@namei.org, spender@grsecurity.net, dwalsh@redhat.com,
cl@linux-foundation.org, arjan@infradead.org, kyle@mcmartin.ca,
cpardy@redhat.com, arnd@arndb.de
Subject: Re: [PATCH 1/2] VM/SELinux: require CAP_SYS_RAWIO for all mmap_zero operations
Date: Tue, 21 Jul 2009 16:04:37 +0100 [thread overview]
Message-ID: <20090721160437.5bda68b4@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090721144157.14159.23439.stgit@paris.rdu.redhat.com>
On Tue, 21 Jul 2009 10:41:58 -0400
Eric Paris <eparis@redhat.com> wrote:
> Currently non-SELinux systems need CAP_SYS_RAWIO for an application to mmap
> the 0 page. On SELinux systems they need a specific SELinux permission,
> but do not need CAP_SYS_RAWIO. This has proved to be a poor decision by
> the SELinux team as, by default, SELinux users are logged in unconfined and
> thus a malicious non-root has nothing stopping them from mapping the 0 page
> of virtual memory.
So the poor decision is in fact that the SELinux users start as
unconfined rather than taking away a few things like the the min map
stuff which can then be given back to specific apps.
> On a non-SELinux system, a malicious non-root user is unable to do this, as
> they need CAP_SYS_RAWIO.
>
> This patch checks CAP_SYS_RAWIO for all operations which attemt to map a
> page below mmap_min_addr.
So "wine" now needs to run with CAP_SYS_RAWIO or you turn all the
security off.
Am I missing something here, this "solution" sounds completely brain
dead ?
Alan
next prev parent reply other threads:[~2009-07-21 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 14:41 Eric Paris
2009-07-21 14:42 ` [PATCH 2/2] SELinux: selinux_file_mmap always enforce mapping the 0 page Eric Paris
2009-07-21 15:04 ` Alan Cox [this message]
2009-07-21 15:18 ` [PATCH 1/2] VM/SELinux: require CAP_SYS_RAWIO for all mmap_zero operations Eric Paris
2009-07-21 15:38 ` Alan Cox
2009-07-21 15:57 ` Eric Paris
2009-07-21 16:09 ` Alan Cox
2009-07-21 16:23 ` Eric Paris
2009-07-21 16:30 ` Alan Cox
2009-07-29 15: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=20090721160437.5bda68b4@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=arnd@arndb.de \
--cc=cl@linux-foundation.org \
--cc=cpardy@redhat.com \
--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
all inboxes | Powered by JetHome®