diff options
| author | Kees Cook <keescook@chromium.org> | 2019-09-04 09:24:49 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-09-05 07:43:34 +0200 |
| commit | f56f791f6d8e8296c9dd194506ee2b703b1227d4 (patch) | |
| tree | 8289ce48488211126ee67b256c5805480690b9f6 | |
| parent | 02e740aeca79e9a3c464bc2ebb510457c85d2015 (diff) | |
| download | linux-stable-f56f791f6d8e8296c9dd194506ee2b703b1227d4.tar.gz linux-stable-f56f791f6d8e8296c9dd194506ee2b703b1227d4.tar.bz2 linux-stable-f56f791f6d8e8296c9dd194506ee2b703b1227d4.zip | |
Documentation/process: Add Google contact for embargoed hardware issues
This adds myself as the Google contact for embargoed hardware security
issues and fixes some small typos.
Cc: Thomas Gleixner <tglx@linutronix.de>
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>
Link: https://lore.kernel.org/r/201909040922.56496BF70@keescook
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | Documentation/process/embargoed-hardware-issues.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst index f9e8c0b23c52..47316d9c24f5 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 |