linux-kernel - Re: Is PIE randomization breaking klibc binaries?

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]

Message-ID: <20070802204216.GA10311@deine-taler.de>
Date:	Thu, 2 Aug 2007 22:42:16 +0200
From:	Ulrich Kunitz <kune@...ne-taler.de>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Sergey Vlasov <vsu@...linux.ru>, Chuck Ebbert <cebbert@...hat.com>,
	linux-kernel@...r.kernel.org, honza@...os.cz, jkosina@...e.cz
Subject: Re: Is PIE randomization breaking klibc binaries?

H. Peter Anvin wrote:

> Yup... it should probably be pointed out the reason the old kernel 
> worked was nothing but pure dumb luck.  This was a GNU ld change which 
> needed to be undone for klibc.  It's unfortunate that stock x86-64 
> binaries leave as little of a null pointer range as they do, but that's 
> life, unfortunately.  The other alternative is to map klibc just below 
> the 2 GB point, which would also work, but the old way broke when the ld 
> change went in.  As previously stated, klibc-1.4.35 or higher fixes this.
> 
> 	-hpa

Just for the record: The kernel with the PIE patch boots perfectly
using the klibc 1.5 shared binaries on my machine.

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