linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: linux-mm@kvack.org
Subject: Prevent self modifying code.
Date: Mon, 09 Oct 2006 17:18:23 +0100	[thread overview]
Message-ID: <452A764F.2010609@superbug.demon.co.uk> (raw)

Hi,

1) In linux, is it possible to enforce that all pages with executable
program code are automatically marked read-only? I.e. to actively
prevent any self modifying code.
2) I know there is a NX(no execute) bit. Is that automatically applied
to all read-write pages? i.e to stack and data pages.
3) Is it possible to ensure that the kernel is the only place that can
take files with the +x bit set, and load the program code into memory
then mark it as read-only, executable pages.
4) Is it possible to ensure that all jump tables used by the executable
code are also read-only?

James




--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2006-10-09 16:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=452A764F.2010609@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=linux-mm@kvack.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