linux-kernel - Re: Executable file format, locating stack?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 1 Dec 2007 12:42:42 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Joshua Hudson" <joshudson@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Executable file format, locating stack?

On Sat, 1 Dec 2007 10:09:28 -0800
"Joshua Hudson" <joshudson@...il.com> wrote:

> Is there an executable file format that can specify things like where
> the stack ends up?
> Yes, I really do care. I want to put the stack at the top of virtual
> address space rather than randomized.

just set the personality with setarch if you don't want randomisation.

Why is it that you can't cope with randomization? You'll have SOME
randomziation no matter what because each glibc compile will have a
slightly different footprint on the stack before your app gets to it,
as do the various environment variables and kernel AT_ variables.

-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/