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:38:13 +0100 [thread overview]
Message-ID: <20090721163813.0cb5d7ab@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1248189524.2654.301.camel@localhost>
> turns it off for the whole system when you install WINE. This patch
> doesn't change that fact. All it does is add that requirement to
> SELinux systems that already exists on non-selinux systems.
Prior to this an SELinux system could implement sensible security. The
fact Fedora didn't was paranoia and fear over a bad experience made what
five years ago ?
> > Am I missing something here, this "solution" sounds completely brain
> > dead ?
>
> Well, with patch 2/2 you still get your SELinux protections (only for 1
> page) even if you disable it for the whole system. So in the end, you
> have better protection than you have today with this series....
We know one page isn't sufficient. That has been seen from some exploit
cases.
So this looks to me like a regression in features, that makes the system
less secure and doesn't solve anything at all.
Whereas if you just set the default SELinux user confinement to allow
everything but mapping low pages you wouldn't actually need to mess up
the kernel ?
Currently I have low page protection and I don't have to run wine as
CAP_SYS_RAWIO (which comes in the "sucidial ideas") category. I consider
the loss of that ability a regression.
Alan
next prev parent reply other threads:[~2009-07-21 15:38 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 ` [PATCH 1/2] VM/SELinux: require CAP_SYS_RAWIO for all mmap_zero operations Alan Cox
2009-07-21 15:18 ` Eric Paris
2009-07-21 15:38 ` Alan Cox [this message]
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=20090721163813.0cb5d7ab@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®