diff options
Diffstat (limited to 'Documentation/process/embargoed-hardware-issues.rst')
| -rw-r--r-- | Documentation/process/embargoed-hardware-issues.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst index d37cbc502936..402636356fbe 100644 --- a/Documentation/process/embargoed-hardware-issues.rst +++ b/Documentation/process/embargoed-hardware-issues.rst | |||
| @@ -5,7 +5,7 @@ Scope | |||
| 5 | ----- | 5 | ----- |
| 6 | 6 | ||
| 7 | Hardware issues which result in security problems are a different category | 7 | Hardware issues which result in security problems are a different category |
| 8 | of security bugs than pure software bugs which only affect the Linux | 8 | of security bugs than pure software bugs which only affect the Linux |
| 9 | kernel. | 9 | kernel. |
| 10 | 10 | ||
| 11 | Hardware issues like Meltdown, Spectre, L1TF etc. must be treated | 11 | Hardware issues like Meltdown, Spectre, L1TF etc. must be treated |
| @@ -159,7 +159,7 @@ Mitigation development | |||
| 159 | 159 | ||
| 160 | The initial response team sets up an encrypted mailing-list or repurposes | 160 | The initial response team sets up an encrypted mailing-list or repurposes |
| 161 | an existing one if appropriate. The disclosing party should provide a list | 161 | an existing one if appropriate. The disclosing party should provide a list |
| 162 | of contacts for all other parties who have already been, or should be | 162 | of contacts for all other parties who have already been, or should be, |
| 163 | informed about the issue. The response team contacts these parties so they | 163 | informed about the issue. The response team contacts these parties so they |
| 164 | can name experts who should be subscribed to the mailing-list. | 164 | can name experts who should be subscribed to the mailing-list. |
| 165 | 165 | ||
| @@ -217,11 +217,11 @@ an involved disclosed party. The current ambassadors list: | |||
| 217 | AMD | 217 | AMD |
| 218 | IBM | 218 | IBM |
| 219 | Intel | 219 | Intel |
| 220 | Qualcomm | 220 | Qualcomm Trilok Soni <tsoni@codeaurora.org> |
| 221 | 221 | ||
| 222 | Microsoft | 222 | Microsoft Sasha Levin <sashal@kernel.org> |
| 223 | VMware | 223 | VMware |
| 224 | XEN | 224 | Xen Andrew Cooper <andrew.cooper3@citrix.com> |
| 225 | 225 | ||
| 226 | Canonical Tyler Hicks <tyhicks@canonical.com> | 226 | Canonical Tyler Hicks <tyhicks@canonical.com> |
| 227 | Debian Ben Hutchings <ben@decadent.org.uk> | 227 | Debian Ben Hutchings <ben@decadent.org.uk> |
| @@ -230,8 +230,8 @@ an involved disclosed party. The current ambassadors list: | |||
| 230 | SUSE Jiri Kosina <jkosina@suse.cz> | 230 | SUSE Jiri Kosina <jkosina@suse.cz> |
| 231 | 231 | ||
| 232 | Amazon | 232 | Amazon |
| 233 | 233 | Google Kees Cook <keescook@chromium.org> | |
| 234 | ============== ======================================================== | 234 | ============= ======================================================== |
| 235 | 235 | ||
| 236 | If you want your organization to be added to the ambassadors list, please | 236 | If you want your organization to be added to the ambassadors list, please |
| 237 | contact the hardware security team. The nominated ambassador has to | 237 | contact the hardware security team. The nominated ambassador has to |
