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]

Date:	Tue, 31 Jul 2007 08:15:34 -0400
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	Ulrich Kunitz <kune@...ne-taler.de>,
	Chuck Ebbert <cebbert@...hat.com>,
	linux-kernel@...r.kernel.org, Jan Kratochvil <honza@...os.cz>,
	jakub@...hat.com
Subject: Re: Is PIE randomization breaking klibc binaries?

Jiri Kosina wrote:
> On Tue, 31 Jul 2007, H. Peter Anvin wrote:
> 
>>> I just now quickly tried to with klibc-1.5 on i386 with the 
>>> PIE-randomization patched kernel, and it seems to load static 
>>> libraries fine. I just downloaded klibc-1.5, built it, and executed a 
>>> few of the programs in usr/utils/static, all of them worked. Does this 
>>> also work for you and you are experiencing the problems solely when 
>>> the binaries are being run from initramfs during boot? I will test 
>>> more shortly (on x86_64, directly from initramfs) in order to 
>>> reproduce.
>> What about shared binaries?
> 
> Works for me too on the pie-randomization patched kernel.
> 
> So it seems to me that either it is something x86_64 specific or 
> initramfs-specific. Will try to reproduce it.
> 

My guess would be the former, rather than the latter.  I haven't had a 
chance to reproduce it myself yet (I'm on the road), but I will try to 
get the time tomorrow.
-
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/