From: Eric Paris <eparis@redhat.com>
To: Alan Cox <alan@redhat.com>
Cc: James Morris <jmorris@namei.org>,
linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov,
drepper@redhat.com, roland@redhat.com, arjan@infradead.org,
mingo@elte.hu, viro@zeniv.linux.org.uk, chrisw@redhat.com,
sds@tycho.nsa.gov, sgrubb@redhat.com
Subject: Re: [PATCH] Protection for exploiting null dereference using mmap
Date: Tue, 05 Jun 2007 17:28:47 -0400 [thread overview]
Message-ID: <1181078927.3978.42.camel@localhost.localdomain> (raw)
In-Reply-To: <20070605211616.GE23291@devserv.devel.redhat.com>
On Tue, 2007-06-05 at 17:16 -0400, Alan Cox wrote:
> On Tue, Jun 05, 2007 at 05:00:51PM -0400, James Morris wrote:
> > This should be an unsigned long.
> >
> > I wonder if the default should be for this value to be zero (i.e. preserve
> > existing behavior). It could break binaries, albeit potentially insecure
>
> Agreed - DOSemu type apps and lrmi need to map at zero for vm86
While I understand, there are a few users who will have problems with
this default are we really better to not provide this defense in depth
for the majority of users and let those with problems turn it off rather
than provide no defense by default? I could even provide a different
default for SELinux and non-SELinux if anyone saw value in that? But if
others think that off default is best I'll send another patch shortly
with the unsigned long fix and the default set to 0. My hope is then
that distros will figure out to turn this on.
-Eric
next prev parent reply other threads:[~2007-06-05 21:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1180561713.3633.27.camel@dhcp231-215.rdu.redhat.com>
[not found] ` <20070603205653.GE25869@devserv.devel.redhat.com>
[not found] ` <1180964306.14220.34.camel@moss-spartans.epoch.ncsc.mil>
2007-06-05 20:34 ` [PATCH] Protection for exploiting null dereference using mmap Eric Paris
2007-06-05 21:00 ` James Morris
2007-06-05 21:16 ` Alan Cox
2007-06-05 21:28 ` Eric Paris [this message]
2007-06-05 22:46 ` H. Peter Anvin
2007-06-07 14:28 ` Pavel Machek
2007-06-06 12:47 ` Stephen Smalley
2007-06-07 16:58 ` Jan Engelhardt
2007-06-06 6:30 ` Eric Paris
2007-06-06 13:21 ` James Morris
2007-06-06 17:30 ` Stephen Smalley
2007-06-06 18:01 ` James Morris
2007-06-06 18:06 ` Chris Wright
2007-06-20 19:48 ` Adam Jackson
2007-06-05 22:49 ` Chris Wright
2007-06-05 22:53 ` Chris Wright
2007-06-06 12:12 ` Stephen Smalley
2007-06-06 9:01 ` Russell Coker
2007-06-06 12:18 ` Stephen Smalley
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=1181078927.3978.42.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=alan@redhat.com \
--cc=arjan@infradead.org \
--cc=chrisw@redhat.com \
--cc=drepper@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=sgrubb@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).