linux-kernel - Re: [PATCH] x86, kaslr: propagate base load address calculation

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 11 Feb 2015 00:13:30 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Kees Cook <keescook@...omium.org>
cc:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>,
	live-patching@...r.kernel.org, Linux-MM <linux-mm@...ck.org>,
	"x86@...nel.org" <x86@...nel.org>
Subject: Re: [PATCH] x86, kaslr: propagate base load address calculation

On Wed, 11 Feb 2015, Jiri Kosina wrote:

> Alternatively, we can forbid zero-sized randomization, and always enforce 
> at least some minimal offset to be chosen in case zero would be chosen.

Okay, I see, that might not be always possible, depending on the memory 
map layout.

So I'll just send you a respin of my previous patch tomorrow that would, 
instead of defining __KERNEL_OFFSET as a particular value, introduce a 
simple global flag which would indicate whether kaslr is in place or not.

-- 
Jiri Kosina
SUSE Labs
--
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/