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  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:	Mon, 22 Dec 2014 20:49:54 +0100 (CET)
From:	Jiri Kosina <>
To:	Andy Lutomirski <>
cc:	Hector Marco Gisbert <>,
	Cyrill Gorcunov <>,
	Pavel Emelyanov <>,
	Catalin Marinas <>,
	Heiko Carstens <>,
	Oleg Nesterov <>,
	Ingo Molnar <>,
	Anton Blanchard <>,
	Russell King - ARM Linux <>,
	"H. Peter Anvin" <>,
	David Daney <>,
	Andrew Morton <>,
	Arun Chandran <>,
	"" <>,
	Martin Schwidefsky <>,
	Ismael Ripoll <>,
	Christian Borntraeger <>,
	Thomas Gleixner <>,
	Hanno Böck <>,
	Will Deacon <>,
	Benjamin Herrenschmidt <>,
	Kees Cook <>,
	Reno Robert <>
Subject: Re: [PATCH] ASLRv3: randomize_va_space=3 preventing offset2lib

On Mon, 22 Dec 2014, Andy Lutomirski wrote:

> a. With PIE executables, the offset from the executable to the
> libraries is constant.  This is unfortunate when your threat model
> allows you to learn the executable base address and all your gadgets
> are in shared libraries.

When I was originally pushing PIE executable randomization, I have been 
thinking about ways to solve this.

In theory, we could start playing games with load_addr in 
load_elf_interp() and randomizing it completely independently from mmap() 
base randomization, but the question is whether it's really worth the 
hassle and binfmt_elf code complication. I am not convinced.

Jiri Kosina
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists