From: Xavier Bestel <xavier.bestel@free.fr>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Emmanuel Fleury <emmanuel.fleury@labri.fr>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to enable/disable security features on mmap() ?
Date: Thu, 08 Dec 2005 17:20:14 +0100 [thread overview]
Message-ID: <1134058814.1615.176.camel@capoeira> (raw)
In-Reply-To: <Pine.LNX.4.61.0512081051250.13997@chaos.analogic.com>
On Thu, 2005-12-08 at 17:08, linux-os (Dick Johnson) wrote:
> An 8 megabyte variation is absolutely insane. It follows the "If a
> little is good, more must be better..." theory. The purpose of
> the random stack start, initially proposed by me BTW, was to
> prevent stack-exploit code from being able to hard-code addresses
> on the stack. Being off by one byte is enough, 8192 was originally
> discussed and, I thought, adopted. Eight megabytes is absurd and has
> no technical basis.
If you only randomize by one or two bytes, the attacker just has to
retry once or twice to have his exploit work. Even once in 1024 may be
too much for some security-conscious people. The larger the area (with a
fixed step), the less statistically efficient the rootkit.
Xav
next prev parent reply other threads:[~2005-12-08 16:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 14:10 How to enable/disable security features on mmap() ? Emmanuel Fleury
2005-12-08 14:14 ` Arjan van de Ven
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 [this message]
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=1134058814.1615.176.camel@capoeira \
--to=xavier.bestel@free.fr \
--cc=arjan@infradead.org \
--cc=emmanuel.fleury@labri.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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