* [PATCH] Documentation/process: Add Google contact for embargoed hardware issues
@ 2019-09-04 16:24 Kees Cook
2019-09-04 17:25 ` Guenter Roeck
0 siblings, 1 reply; 2+ messages in thread
From: Kees Cook @ 2019-09-04 16:24 UTC (permalink / raw)
To: Thomas Gleixner
Cc: Greg Kroah-Hartman, Linus Torvalds, Tyler Hicks, Ben Hutchings,
Konrad Rzeszutek Wilk, Josh Poimboeuf, Jiri Kosina,
Guenter Roeck, Matt Linton, Matthew Garrett, linux-kernel
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>
---
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Documentation/process: Add Google contact for embargoed hardware issues
2019-09-04 16:24 [PATCH] Documentation/process: Add Google contact for embargoed hardware issues Kees Cook
@ 2019-09-04 17:25 ` Guenter Roeck
0 siblings, 0 replies; 2+ messages in thread
From: Guenter Roeck @ 2019-09-04 17:25 UTC (permalink / raw)
To: Kees Cook
Cc: Thomas Gleixner, Greg Kroah-Hartman, Linus Torvalds, Tyler Hicks,
Ben Hutchings, Konrad Rzeszutek Wilk, Josh Poimboeuf,
Jiri Kosina, Matt Linton, Matthew Garrett, linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-09-04 17:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).