| 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
| ||
|
Date: Wed, 11 Dec 2013 09:06:15 +1030 From: Alan Modra <amodra@...il.com> To: "H.J. Lu" <hjl.tools@...il.com> Cc: LKML <linux-kernel@...r.kernel.org>, Binutils <binutils@...rceware.org> Subject: Re: RFC: binutils PATCH: Set e_type to ET_EXEC for -pie -Ttext-segment= On Mon, Dec 09, 2013 at 07:10:23PM -0800, H.J. Lu wrote: > Linker sets e_type in ELF header to ET_DYN for -pie -Ttext-segment=0xXXX. > When I added -Ttext-segment=0xXXX, one goal was to load > small model executable above 4GB on Linux/x86-64, which > was done with -pie -Ttext-segment=0xXXX. But -pie sets > e_type in ELF header to ET_DYN and kernel may ignore > p_vaddr in ELF header to load ET_DYN binary at a random > address. This patch changes ld to set e_type in ELF header > to ET_EXEC if the first PT_LOAD segment has non-zero > p_vaddr. If this is unacceptable as generic ELF change, > I can make it specific to x86. Well, I suppose it's a hack to use ET_DYN for executables in the first place, so one more hack in the linker hardly matters. Why not just patch the kernel though? The kernel can look at the first PT_LOAD header just as easily as the linker, and it's the kernel that is doing the loading after all. -- Alan Modra Australia Development Lab, IBM -- 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/
Powered by blists - more mailing lists