[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16dc4736-347a-4102-b21b-0e35e060108b@email.android.com>
Date: Mon, 08 Apr 2013 07:58:23 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Ingo Molnar <mingo@...nel.org>
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
Not if we do it right, but there is a huge potential boot time penalty.
Ingo Molnar <mingo@...nel.org> wrote:
>
>* 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
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
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.
