From: Samium Gromoff <_deepfire@feelingofgreen.ru>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Samium Gromoff <_deepfire@feelingofgreen.ru>,
Pavel Machek <pavel@ucw.cz>,
Valdis.Kletnieks@vt.edu, David Wagner <daw@cs.berkeley.edu>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Mechanism to turn of ASR on a per-ELF binary basis
Date: Tue, 23 Jan 2007 23:21:32 +0300 [thread overview]
Message-ID: <878xft8pf7.wl@betelheise.deep.net> (raw)
In-Reply-To: <20070123154127.57059632@localhost.localdomain>
These patches allow the binaries which absolutely require that
their address space layout to be unaffected by address space
randomisation to specify that in their ELF header.
The first part defines the ELF header flag, the second implements
the corresponding part of the interpreter functionality.
regards, Samium Gromoff
next prev parent reply other threads:[~2007-01-23 20:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 23:23 [PATCH] Undo some of the pseudo-security madness Samium Gromoff
2007-01-21 23:34 ` David Wagner
2007-01-22 0:36 ` Kyle Moffett
2007-01-22 1:53 ` Samium Gromoff
2007-02-24 9:40 ` Florian Weimer
2007-02-24 13:33 ` Samium Gromoff
2007-02-24 13:49 ` Florian Weimer
2007-01-22 15:20 ` Valdis.Kletnieks
2007-01-22 17:39 ` Samium Gromoff
2007-01-23 8:48 ` Pavel Machek
2007-01-23 14:03 ` Samium Gromoff
2007-01-23 15:41 ` Alan
2007-01-23 20:21 ` Samium Gromoff [this message]
2007-01-23 20:28 ` [PATCH 1/2] Define the EF_AS_NO_RANDOM e_flag bit Samium Gromoff
2007-01-23 20:50 ` Jakub Jelinek
2007-01-23 21:06 ` Samium Gromoff
2007-01-23 21:16 ` Jakub Jelinek
2007-01-23 21:54 ` Samium Gromoff
2007-01-23 23:21 ` Samium Gromoff
2007-01-24 17:08 ` Pavel Machek
2007-01-29 1:18 ` Arjan van de Ven
2007-01-23 20:31 ` [PATCH 2/2] Make the EF_AS_NO_RANDOM e_flag bit disable PF_RANDOMIZE Samium Gromoff
2007-02-24 9:51 ` [PATCH] Undo some of the pseudo-security madness Florian Weimer
2007-02-24 13:36 ` Samium Gromoff
2007-01-31 9:59 ` Arjan van de Ven
2007-02-01 8:05 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878xft8pf7.wl@betelheise.deep.net \
--to=_deepfire@feelingofgreen.ru \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daw@cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox