From: Greg KH <greg@kroah.com>
To: kernel-hardening@lists.openwall.com
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [kernel-hardening] [PATCH] doc: self-protection: provide initial details
Date: Mon, 16 May 2016 19:37:10 -0700 [thread overview]
Message-ID: <20160517023710.GA14736@kroah.com> (raw)
In-Reply-To: <20160517022728.GA2821@www.outflux.net>
On Mon, May 16, 2016 at 07:27:28PM -0700, Kees Cook wrote:
> This document attempts to codify the intent around kernel self-protection
> along with discussion of both existing and desired technologies, with
> attention given to the rationale behind them, and the expectations of
> their usage.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Documentation/security/self-protection.txt | 261 +++++++++++++++++++++++++++++
> 1 file changed, 261 insertions(+)
> create mode 100644 Documentation/security/self-protection.txt
Nice job:
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2016-05-17 2:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 2:27 [kernel-hardening] [PATCH] doc: self-protection: provide initial details Kees Cook
2016-05-17 2:27 ` Kees Cook
2016-05-17 2:37 ` Greg KH [this message]
2016-05-17 15:32 ` [kernel-hardening] " Randy Dunlap
2016-05-17 15:32 ` Randy Dunlap
2016-05-17 22:26 ` [kernel-hardening] " Jonathan Corbet
2016-05-17 22:26 ` Jonathan Corbet
2016-05-18 1:44 ` [kernel-hardening] " Kees Cook
2016-05-18 1:44 ` Kees Cook
2016-05-23 9:29 ` [kernel-hardening] " James Morris
2016-05-23 9:29 ` James Morris
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=20160517023710.GA14736@kroah.com \
--to=greg@kroah.com \
--cc=corbet@lwn.net \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--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 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.