From: Arjan van de Ven <arjan@infradead.org>
To: David Jacoby <dj@outpost24.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stack guards, PaX and such
Date: Thu, 30 Dec 2004 11:02:56 +0100 [thread overview]
Message-ID: <1104400976.4170.7.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <41D3C66F.5070909@outpost24.com>
On Thu, 2004-12-30 at 10:12 +0100, David Jacoby wrote:
> Hi everyone!
>
> I hope you had an nice and relaxing x-mas and are ready for a nice new
> years eve.
> I just have a little question, i really dont if this has ben discussed
> before, but if it
> has im really sorry.
are you talking about making the userspace stack not executable or the
kernel stacks?
With NX, userspace stacks already are not executable (and if you have a
cpu without NX you can use the execshield patches or PaX)
As for kernel stacks, well, with NX those are not executable either, and
to be honest, I can't remember the last time there was a user
exploitable kernel stack buffer overflow. So if your assertion is that
those are a common type of security problem, I disagree with you.
(One of the underlying causes is that the kernel stack is only really
small so it's relatively uncommon and deprecated to put arrays on the
kernel stack)
prev parent reply other threads:[~2004-12-30 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 9:12 David Jacoby
2004-12-30 10:02 ` Arjan van de Ven [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=1104400976.4170.7.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=dj@outpost24.com \
--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®