[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110531202712.GB28731@elte.hu>
Date: Tue, 31 May 2011 22:27:12 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Dan Rosenberg <drosenberg@...curity.com>,
Matthew Garrett <mjg@...hat.com>,
Tony Luck <tony.luck@...il.com>, linux-kernel@...r.kernel.org,
kees.cook@...onical.com, davej@...hat.com,
torvalds@...ux-foundation.org, adobriyan@...il.com,
eranian@...gle.com, penberg@...nel.org, davem@...emloft.net,
Arjan van de Ven <arjan@...radead.org>,
Valdis.Kletnieks@...edu, Andrew Morton <akpm@...ux-foundation.org>,
pageexec@...email.hu, Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [RFC][PATCH] Randomize kernel base address on boot
* H. Peter Anvin <hpa@...or.com> wrote:
> On 05/31/2011 12:55 PM, Ingo Molnar wrote:
> >
> > So ... could you *please* not shelf this idea just because people
> > used lkml for what it was invented: argued with each other rather
> > forcefully? :-)
>
> The real issue is that if it can be (semi)trivially bypassed, then
> there may not be much reason to do it.
Sure.
> Other than that, Ingo's idea at least have the merit that it would
> break only older bootloaders doing things wrong.
I'm wondering, why would it break older bootloaders? It's just a
slightly larger than usual kernel image, nothing is visible to the
bootloader.
Thanks,
Ingo
--
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