From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [PATCH] doc: self-protection: provide initial details
Date: Tue, 17 May 2016 16:26:18 -0600 [thread overview]
Message-ID: <20160517162618.53a9494f@lwn.net> (raw)
In-Reply-To: <20160517022728.GA2821@www.outflux.net>
On Mon, 16 May 2016 19:27:28 -0700
Kees Cook <keescook@chromium.org> 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.
I've applied this to the docs tree. In the process, I took the liberty
of applying the suggestions from Randy, hope you don't mind...
Thanks,
jon
next prev parent reply other threads:[~2016-05-17 22:26 UTC|newest]
Thread overview: 6+ 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:37 ` Greg KH
2016-05-17 15:32 ` [kernel-hardening] " Randy Dunlap
2016-05-17 22:26 ` Jonathan Corbet [this message]
2016-05-18 1:44 ` Kees Cook
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=20160517162618.53a9494f@lwn.net \
--to=corbet@lwn.net \
--cc=keescook@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox