Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130408115823.GC7513@gmail.com>
Date: Mon, 8 Apr 2013 13:58:23 +0200
From: Ingo Molnar <mingo@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
	kernel-hardening@...ts.openwall.com,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Jarkko Sakkinen <jarkko.sakkinen@...el.com>,
	Matthew Garrett <mjg@...hat.com>,
	Matt Fleming <matt.fleming@...el.com>,
	Eric Northup <digitaleric@...gle.com>,
	Dan Rosenberg <drosenberg@...curity.com>,
	Julien Tinnes <jln@...gle.com>, Will Drewry <wad@...omium.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 3/3] x86: kernel base offset ASLR


* H. Peter Anvin <hpa@...or.com> wrote:

> On 04/05/2013 01:04 AM, Ingo Molnar wrote:
> > 
> > Random runtime shuffling of the kernel image - is that possible with 
> > existing toolchains?
> > 
> 
> Yes... the question is how much work we'd be willing to go through to make it 
> happen.
> 
> One approach: the kernel already contains a linker -- used for modules -- and 
> the bulk of the kernel could actually be composed to a "pile of modules" that 
> gets linked on boot.  This would provide very large amounts of randomness.

Is there no code generation / micro-performance disadvantage to that?

Thanks,

	Ingo

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.