From: Rik van Riel <riel@redhat.com>
To: kernel-hardening@lists.openwall.com
Cc: Kees Cook <keescook@chromium.org>
Subject: Re: [kernel-hardening] patches for __write_rarely section
Date: Wed, 16 Nov 2016 10:22:57 -0500 [thread overview]
Message-ID: <1479309777.21171.27.camel@redhat.com> (raw)
In-Reply-To: <CAAseMr6Fae=4otZZX9HmO1YgehjsVmd+44G5RN7Wu8iF2+fruA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Wed, 2016-11-16 at 22:39 +0800, Gengjia Chen wrote:
> Hello kees and everyone :
>
> This email introduces two patches.
>
> Patch 1 introduce the write-rarely memory section for
> those kernel objects which are read only mostly
> but need to be written to sometimes.
>
> Patch 2 introduce two helper functions (mark_wrdata_rw/
> mark_wrdata_ro) to make __write_rarely memory section
> writable or unwritable. They play like the pax_open_kernel/
> pax_close_kernel functions in grsecurity patch.Right now
> this only been implemented on arm32.
Is this the way we want to go with this, or could it
make more sense to have a special ELF section in the
kernel that is allowed to write to write-rarely memory,
and have the exception handler deal with writes coming
from that code?
That way it would be much harder to insert code into the
kernel that calls your mark_wrdata_rw/mark_wrdata_ro
functions.
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-11-16 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 14:39 [kernel-hardening] patches for __write_rarely section Gengjia Chen
2016-11-16 15:16 ` Mark Rutland
2016-11-17 23:47 ` Kees Cook
2016-11-18 11:10 ` Mark Rutland
2016-11-18 11:42 ` Mark Rutland
2016-11-16 15:22 ` Rik van Riel [this message]
2016-11-16 16:14 ` Greg KH
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=1479309777.21171.27.camel@redhat.com \
--to=riel@redhat.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.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 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.