From: Andreas Steinmetz <ast@domdv.de>
To: "H. J. Lu" <hjl@lucon.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to make stack executable on demand?
Date: Fri, 16 Apr 2004 20:07:30 +0200 [thread overview]
Message-ID: <408020E2.9060900@domdv.de> (raw)
In-Reply-To: <20040416170915.GA20260@lucon.org>
H. J. Lu wrote:
> is set with executable stack. Is there a third option that a process
> starts with non-executable stack and can change the stack permission
> later?
>
Well, in my opinion your request is equivalent to "keep all these cute
buffer overflows forever". Take any protected app, LD_PRELOAD or drop in
a bad/malicious library and your're done for good. Not really a good idea.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
next prev parent reply other threads:[~2004-04-16 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 17:09 How to make stack executable on demand? H. J. Lu
2004-04-16 18:07 ` Andreas Steinmetz [this message]
2004-04-16 19:40 ` H. J. Lu
2004-04-19 14:39 ` Pavel Machek
2004-04-16 20:02 ` Arjan van de Ven
2004-04-16 20:46 ` H. J. Lu
2004-04-16 20:57 ` Dave Jones
2004-04-17 7:13 ` Arjan van de Ven
2004-04-19 0:08 ` Jamie Lokier
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=408020E2.9060900@domdv.de \
--to=ast@domdv.de \
--cc=hjl@lucon.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.