From: Patrick E Kane <kane@urbana.css.mot.com>
To: phoebe-list@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stack growing and buffer overflows
Date: Mon, 10 Mar 2003 17:29:35 -0600 [thread overview]
Message-ID: <20030310172935.A1324@scapula.urbana.css.mot.com> (raw)
In-Reply-To: <20030310230012.26391.qmail@linuxmail.org>; from felipe_alfaro@linuxmail.org on Tue, Mar 11, 2003 at 12:00:12AM +0100
The OpenBSD guys have been working on closing buffer overflow holes.
Slashdot has this pointer to a msg from Theo de Raadt:
http://groups.google.com/groups?selm=b1aq2h%242q9g%241%40FreeBSD.csie.NCTU.edu.tw&output=gplain
In the last while, a couple of people in OpenBSD have
been putting some buffer overflow "solutions" into our
source tree; under my continual prodding. I thought I
would summarize some of these and how they fit together,
since what I have seen written up so far has been
wildly inaccurate. (Bad reporter, no cookie).
These are, in short form:
1) PROT_* purity
2) W^X
3) .rodata
4) propolice
...
I like the idea of turning off execute permission on the stack pages.
PEK
---
next prev parent reply other threads:[~2003-03-10 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 23:00 Felipe Alfaro Solana
2003-03-10 23:29 ` Patrick E Kane [this message]
2003-03-11 10:07 ` Helge Hafting
2003-03-11 12:23 ` =?unknown-8bit?Q?J=F6rn?= Engel
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=20030310172935.A1324@scapula.urbana.css.mot.com \
--to=kane@urbana.css.mot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phoebe-list@redhat.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
all inboxes | Powered by JetHome®