[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070824091720.4c6f4227@laptopd505.fenrus.org>
Date: Fri, 24 Aug 2007 09:17:20 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Jiri Kosina <jkosina@...e.cz>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Zan Lynx <zlynx@....org>, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...e.hu>,
Roland McGrath <roland@...hat.com>,
Jakub Jelinek <jakub@...hat.com>, Kees Cook <kees@...flux.net>
Subject: Re: 2.6.23-rc3-mm1 - memory layout change? - lost support for
MAP_32BIT? - mono crashes
On Fri, 24 Aug 2007 02:09:59 +0200 (CEST)
Jiri Kosina <jkosina@...e.cz> wrote:
> (some more CCs added)
>
> On Thu, 23 Aug 2007, Andrew Morton wrote:
>
> > It is quite unobvious to me that the whole pie-randomization thing
> > is worth merging. Why shouldn't we just drop the lot?
>
> Hi Andrew,
>
> well, whenever it comes to address space layout randomization, there
> usually follows a huge debate whether it is needed or not, some
> people think it's useful and powerful security protection against
> 0day attacks, other people think that it's just fighting the bugs in
> userspace software in a wrong way.
randomizing PIE's is as a whole worth getting right and in mainline.
That means that ONLY the PIE text should be randomized, not that mmap
should break ;)
Randomizing address space is very widely recognized as being part of a
whole set of things (and there's a lot of discussion about what that
whole set should be, each vendor will say their solution should be part
of that and that all others suck) that you need to do to make it a LOT
harder to get a general purpose exploit working. (It's not fool proof;
it's more comparable than a 4 tumble number lock than it is to a iris
scan; yet even a tumble number lock makes it harder to break into your
gym locker)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists