From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: self-protection: rename "leak" to "exposure"
Date: Thu, 9 Jun 2016 13:27:30 -0600 [thread overview]
Message-ID: <20160609132730.369c5649@lwn.net> (raw)
In-Reply-To: <20160518133747.GA13229@www.outflux.net>
On Wed, 18 May 2016 06:37:47 -0700
Kees Cook <keescook@chromium.org> wrote:
> The meaning of "leak" can be both "untracked resource allocation" and
> "memory content disclosure". This document's use was entirely of the
> latter meaning, so avoid the confusion by using the Common Weakness
> Enumeration name for this: Information Exposure (CWE-200). Additionally
> adds a section on structure randomization.
Applied (rather belatedly, sorry) to the docs tree.
jon
prev parent reply other threads:[~2016-06-09 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 13:37 Kees Cook
2016-06-09 19:27 ` Jonathan Corbet [this message]
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=20160609132730.369c5649@lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®