From: Demi Obenour <demiobenour@gmail.com>
To: libffi-discuss@sourceware.org
Subject: Avoid stack/heap executable memory
Date: Tue, 03 May 2016 21:28:00 -0000 [thread overview]
Message-ID: <1462310910.16919.2.camel@gmail.com> (raw)
mmap() is the only (reasonably) portable and secure way to get
executable memory. Â An executable stack or heap makes exploiting
vulnerabilities much easier.
How difficult would this be to implement?
next reply other threads:[~2016-05-03 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 21:28 Demi Obenour [this message]
2016-05-03 23:33 ` Richard Henderson
2016-05-04 10:17 ` Andrew Haley
2016-05-04 12:42 ` Anthony Green
2016-05-04 16:14 ` Jay
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=1462310910.16919.2.camel@gmail.com \
--to=demiobenour@gmail.com \
--cc=libffi-discuss@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).