From: William Lee Irwin III <wli@holomorphy.com>
To: Breno <brenosp@brasilsec.com.br>
Cc: linux-kernel@vger.kernel.org, M?ns Rullg?rd <mru@kth.se>
Subject: Re: Question - non-exec stack
Date: Fri, 28 Nov 2003 13:16:55 -0800 [thread overview]
Message-ID: <20031128211655.GA8039@holomorphy.com> (raw)
In-Reply-To: <001501c3b5b7$84c5bd20$34dfa7c8@bsb.virtua.com.br>
On Fri, Nov 28, 2003 at 11:57:09AM -0200, Breno wrote:
> Yes , 32 bit Intel processors
Due to the really hard drugs the processor designers must have been
on, the only way to implement this is via the particularly nasty flavor
of segmentation on Intel processors (sane forms just use bits in pointers).
c.f. pax and exec-shield for examples of how to do it in Linux (please
do not start that debate; the only relevant point here is they use the
segmentation stuff). I suspect OpenBSD might also implement it.
-- wli
prev parent reply other threads:[~2003-11-28 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 13:29 Question - non-exec stack Breno
2003-11-28 13:44 ` Måns Rullgård
2003-11-28 13:57 ` Breno
2003-11-28 21:16 ` William Lee Irwin III [this message]
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=20031128211655.GA8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=brenosp@brasilsec.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/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;
as well as URLs for NNTP newsgroup(s).