linux-kernel - Re: [RFC][PATCH] Randomize kernel base address on boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 May 2011 16:17:04 -0400
From:	Dan Rosenberg <drosenberg@...curity.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Matthew Garrett <mjg@...hat.com>, "H. Peter Anvin" <hpa@...or.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

On Tue, 2011-05-31 at 21:55 +0200, Ingo Molnar wrote:
> * Dan Rosenberg <drosenberg@...curity.com> wrote:
> 
> > Just for the record, I've put this patch on hold until there's some 
> > more consensus about whether boot-time randomization of the 
> > physical kernel address is the best approach. [...]
> 
> Well, if you use the suggestion i made: to skip the e820 map fiddling 
> altogether and just allocate half a megabyte of 'hole' at the end of 
> the kernel image - which would allow the kernel to be randomized 
> freely upwards by 0-128 pages - then the 'dynamic' versus 'static' 
> solution could be used at once!
> 
> The 'static' method would use the same hole, just at install time, 
> while the 'dynamic' method would use it during bootup.
> 
> Also, if this method is used then most of the controversy about the 
> dynamic approach goes away (which was the memory maps interpretation 
> fragility).
> 
> Your last patch would need only minor modifications to get the hole 
> added: you'd need to add the tail-hole in the linker map:
> 
>    arch/x86/kernel/vmlinux.lds.S
> 
> So ... could you *please* not shelf this idea just because people 
> used lkml for what it was invented: argued with each other rather 
> forcefully? :-)
> 

Don't worry, I haven't shelved the idea...I just wanted to see more of
the on-going conversation before investing a substantial amount of time
on a potentially infeasible solution.  I'll give this approach a shot.

-Dan

> 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/