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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Sat, 15 Sep 2007 10:46:15 +0200
From:	Franck Bui-Huu <vagabon.xyz@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org
Subject: ELF randomization questions 

Hello,

I have a couple questions about the process stack randomization but
I'm not sure who should be CCed for such questions.

I submitted a patch to enable 'inside the page' stack randomization on
MIPS few weeks ago and which has been now committed. But I noticed
that this patch is actually useless because this randomization depends
on ELF_PLATFORM symbol to be defined which it isn't on MIPS. All of
this happens in create_elf_tables() function defined in
fs/binfmt_elf.c.

So my first question is now, why is this dependency for ? Can we
remove it and unconditionally do the 'inside the page' randomization
for platforms that implement it ?  I'm not sure how ELF_PLATFORM is
used, I guess it is used later by ld.so on certain architectures but
dunno how.

The second question is that the stack randomization is currently
mainly part of the elf code, but shouldn't it be put in exec.c and
thus be used by all others binary handlers ?

thanks for any hints.

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