From: Arjan van de Ven <arjan@infradead.org>
To: Emmanuel Fleury <emmanuel.fleury@labri.fr>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to enable/disable security features on mmap() ?
Date: Thu, 08 Dec 2005 15:14:32 +0100 [thread overview]
Message-ID: <1134051272.2867.63.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <43983EBE.2080604@labri.fr>
On Thu, 2005-12-08 at 15:10 +0100, Emmanuel Fleury wrote:
> Hi,
>
> For educational purpose (I'm teaching software security) I would like to
> be able to compile several kernels with or without features such as:
>
> * Non-executable stack
> * Stack address randomization
> * Environment address randomization (char **envp)
> * Dynamic library randomization (cat /proc/self/map)
>
> So, is there a way to do such thing easily, or should I write patches by
> myself ?
realistically the first one is easy if your hw supports the NX bit
(x86/x86-64). Some of the other randomisations are present in the 2.6.x
kernels.
Or run a kernel from Fedora Core, or a kernel with the PaX patches to
get all you're asking for.
next prev parent reply other threads:[~2005-12-08 14:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 14:10 Emmanuel Fleury
2005-12-08 14:14 ` Arjan van de Ven [this message]
2005-12-08 14:21 ` Emmanuel Fleury
2005-12-08 14:39 ` Emmanuel Fleury
2005-12-08 14:49 ` Arjan van de Ven
2005-12-08 14:54 ` Emmanuel Fleury
2005-12-08 15:02 ` Emmanuel Fleury
2005-12-08 15:16 ` linux-os (Dick Johnson)
2005-12-08 15:29 ` Emmanuel Fleury
2005-12-08 15:39 ` Arjan van de Ven
2005-12-08 16:42 ` Nix
2005-12-08 15:37 ` Arjan van de Ven
2005-12-08 16:08 ` linux-os (Dick Johnson)
2005-12-08 16:14 ` Arjan van de Ven
2005-12-08 16:24 ` linux-os (Dick Johnson)
2005-12-08 16:35 ` Arjan van de Ven
2005-12-08 16:20 ` Xavier Bestel
2005-12-08 16:21 ` Arjan van de Ven
2005-12-08 16:30 ` linux-os (Dick Johnson)
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=1134051272.2867.63.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=emmanuel.fleury@labri.fr \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®