linux-kernel - Re: [PATCH 1/2] Define the EF_AS_NO_RANDOM e

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: <1170033494.3054.5.camel@laptopd505.fenrus.org>
Date:	Mon, 29 Jan 2007 09:18:12 +0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Samium Gromoff <_deepfire@...lingofgreen.ru>
Cc:	Alan <alan@...rguk.ukuu.org.uk>, Pavel Machek <pavel@....cz>,
	Valdis.Kletnieks@...edu, David Wagner <daw@...berkeley.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Define the EF_AS_NO_RANDOM e_flag bit

On Tue, 2007-01-23 at 23:28 +0300, Samium Gromoff wrote:
> Author: Samium Gromoff <deepfire@...elheise.deep.net>
> Date:   Tue Jan 23 22:31:13 2007 +0300
> 
>     Define the ELF binary header flag EF_AS_NO_RANDOM
>     
>     EF_AS_NO_RANDOM should mean that the binary requests to not apply
>     randomisation to address spaces of its processes.

sounds like it's not the right approach; better to follow the
PT_GNU_STACK example and do it that way.....

(assuming you even need it... I personally consider every binary that
would need this flag as broken)

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