linux-kernel - Re: [PATCH] binfmt_elf: fix PIE load with randomization disabled

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: <alpine.LNX.2.00.1312111435470.1413@pobox.suse.cz>
Date:	Wed, 11 Dec 2013 14:36:36 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	"H.J. Lu" <hjl.tools@...il.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Josh Boyer <jwboyer@...hat.com>
Subject: Re: [PATCH] binfmt_elf: fix PIE load with randomization disabled

On Mon, 9 Dec 2013, H.J. Lu wrote:

> >> so that he could load his program compiled as PIE above 4GB.
> >> If kernel is changed not to honor it, his program won't work any more.
> >> In normal case, PIE has zero vaddr and this doesn't apply.
> >>
> >
> > That doesn't seem to be PIE at all, and if it is PIE, then it should be
> > relocatable (I agree btw with randomizing upward from the selected address.)
> 
> Kernel can consider PIE with non-zero vaddr isn't real PIE.

Why?

I still think PIE with non-zero vaddr should be randomized by putting 
random offset to the vaddr. Don't you think so? Why?

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