From: Guenter Roeck <linux@roeck-us.net>
To: Kees Cook <keescook@chromium.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tyler Hicks <tyhicks@canonical.com>,
Ben Hutchings <ben@decadent.org.uk>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jiri Kosina <jkosina@suse.cz>, Matt Linton <amuse@google.com>,
Matthew Garrett <mjg59@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/process: Add Google contact for embargoed hardware issues
Date: Wed, 4 Sep 2019 10:25:58 -0700 [thread overview]
Message-ID: <20190904172558.GA24934@roeck-us.net> (raw)
In-Reply-To: <201909040922.56496BF70@keescook>
On Wed, Sep 04, 2019 at 09:24:49AM -0700, Kees Cook wrote:
> This adds myself as the Google contact for embargoed hardware security
> issues and fixes some small typos.
>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Matt Linton <amuse@google.com>
> Cc: Matthew Garrett <mjg59@google.com>
> Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Guenter Roeck <groeck@chromium.org>
> ---
> Documentation/process/embargoed-hardware-issues.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst
> index d37cbc502936..1c1ad684d753 100644
> --- a/Documentation/process/embargoed-hardware-issues.rst
> +++ b/Documentation/process/embargoed-hardware-issues.rst
> @@ -5,7 +5,7 @@ Scope
> -----
>
> Hardware issues which result in security problems are a different category
> -of security bugs than pure software bugs which only affect the Linux
> +of security bugs than pure software bugs which only affect the Linux
> kernel.
>
> Hardware issues like Meltdown, Spectre, L1TF etc. must be treated
> @@ -159,7 +159,7 @@ Mitigation development
>
> The initial response team sets up an encrypted mailing-list or repurposes
> an existing one if appropriate. The disclosing party should provide a list
> -of contacts for all other parties who have already been, or should be
> +of contacts for all other parties who have already been, or should be,
> informed about the issue. The response team contacts these parties so they
> can name experts who should be subscribed to the mailing-list.
>
> @@ -230,8 +230,8 @@ an involved disclosed party. The current ambassadors list:
> SUSE Jiri Kosina <jkosina@suse.cz>
>
> Amazon
> - Google
> - ============== ========================================================
> + Google Kees Cook <keescook@chromium.org>
> + ============= ========================================================
>
> If you want your organization to be added to the ambassadors list, please
> contact the hardware security team. The nominated ambassador has to
> --
> 2.17.1
>
>
> --
> Kees Cook
prev parent reply other threads:[~2019-09-04 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 16:24 [PATCH] Documentation/process: Add Google contact for embargoed hardware issues Kees Cook
2019-09-04 17:25 ` Guenter Roeck [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=20190904172558.GA24934@roeck-us.net \
--to=linux@roeck-us.net \
--cc=amuse@google.com \
--cc=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tyhicks@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).