| Message ID | 20231004004959.work.258-kees@kernel.org (mailing list archive) |
|---|---|
| State | Mainlined |
| Commit | 39fef15b5f2db46619393f9fd20fdd26a2ff49ef |
| Headers | show |
| Series | Documentation: embargoed-hardware-issues.rst: Clarify prenotifaction | expand |
On Tue, Oct 03, 2023 at 05:50:03PM -0700, Kees Cook wrote: > There has been a repeated misunderstanding about what the hardware embargo > list is for. Clarify the language in the process so that it is clear > that only fixes are coordinated. There is explicitly no prenotification > process. The list members are also expected to keep total radio silence > during embargoes. > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> > Cc: Thomas Gleixner <tglx@linutronix.de> > Cc: workflows@vger.kernel.org > Cc: linux-doc@vger.kernel.org > Signed-off-by: Kees Cook <keescook@chromium.org> > --- > .../process/embargoed-hardware-issues.rst | 19 ++++++++++++------- > 1 file changed, 12 insertions(+), 7 deletions(-) > > diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst > index ac7c52f130c9..31000f075707 100644 > --- a/Documentation/process/embargoed-hardware-issues.rst > +++ b/Documentation/process/embargoed-hardware-issues.rst > @@ -25,15 +25,15 @@ Contact > The Linux kernel hardware security team is separate from the regular Linux > kernel security team. > > -The team only handles the coordination of embargoed hardware security > -issues. Reports of pure software security bugs in the Linux kernel are not > +The team only handles developing fixes for embargoed hardware security > +issues. Reports of pure software security bugs in the Linux kernel are not > handled by this team and the reporter will be guided to contact the regular > Linux kernel security team (:ref:`Documentation/admin-guide/ > <securitybugs>`) instead. > > The team can be contacted by email at <hardware-security@kernel.org>. This > -is a private list of security officers who will help you to coordinate an > -issue according to our documented process. > +is a private list of security officers who will help you to coordinate a > +fix according to our documented process. > > The list is encrypted and email to the list can be sent by either PGP or > S/MIME encrypted and must be signed with the reporter's PGP key or S/MIME > @@ -132,11 +132,11 @@ other hardware could be affected. > > The hardware security team will provide an incident-specific encrypted > mailing-list which will be used for initial discussion with the reporter, > -further disclosure and coordination. > +further disclosure, and coordination of fixes. > > The hardware security team will provide the disclosing party a list of > developers (domain experts) who should be informed initially about the > -issue after confirming with the developers that they will adhere to this > +issue after confirming with the developers that they will adhere to this Nit, whitespace change wasn't documented in the changelog :) Thanks for this, it matches up with the list rules now much better (that everyone gets when they join one of these lists), so I'll go apply it to my tree now. greg k-h
diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst index ac7c52f130c9..31000f075707 100644 --- a/Documentation/process/embargoed-hardware-issues.rst +++ b/Documentation/process/embargoed-hardware-issues.rst @@ -25,15 +25,15 @@ Contact The Linux kernel hardware security team is separate from the regular Linux kernel security team. -The team only handles the coordination of embargoed hardware security -issues. Reports of pure software security bugs in the Linux kernel are not +The team only handles developing fixes for embargoed hardware security +issues. Reports of pure software security bugs in the Linux kernel are not handled by this team and the reporter will be guided to contact the regular Linux kernel security team (:ref:`Documentation/admin-guide/ <securitybugs>`) instead. The team can be contacted by email at <hardware-security@kernel.org>. This -is a private list of security officers who will help you to coordinate an -issue according to our documented process. +is a private list of security officers who will help you to coordinate a +fix according to our documented process. The list is encrypted and email to the list can be sent by either PGP or S/MIME encrypted and must be signed with the reporter's PGP key or S/MIME @@ -132,11 +132,11 @@ other hardware could be affected. The hardware security team will provide an incident-specific encrypted mailing-list which will be used for initial discussion with the reporter, -further disclosure and coordination. +further disclosure, and coordination of fixes. The hardware security team will provide the disclosing party a list of developers (domain experts) who should be informed initially about the -issue after confirming with the developers that they will adhere to this +issue after confirming with the developers that they will adhere to this Memorandum of Understanding and the documented process. These developers form the initial response team and will be responsible for handling the issue after initial contact. The hardware security team is supporting the @@ -209,13 +209,18 @@ five work days this is taken as silent acknowledgement. After acknowledgement or resolution of an objection the expert is disclosed by the incident team and brought into the development process. +List participants may not communicate about the issue outside of the +private mailing list. List participants may not use any shared resources +(e.g. employer build farms, CI systems, etc) when working on patches. + Coordinated release """"""""""""""""""" The involved parties will negotiate the date and time where the embargo ends. At that point the prepared mitigations are integrated into the -relevant kernel trees and published. +relevant kernel trees and published. There is no pre-notification process: +fixes are published in public and available to everyone at the same time. While we understand that hardware security issues need coordinated embargo time, the embargo time should be constrained to the minimum time which is
There has been a repeated misunderstanding about what the hardware embargo list is for. Clarify the language in the process so that it is clear that only fixes are coordinated. There is explicitly no prenotification process. The list members are also expected to keep total radio silence during embargoes. Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: workflows@vger.kernel.org Cc: linux-doc@vger.kernel.org Signed-off-by: Kees Cook <keescook@chromium.org> --- .../process/embargoed-hardware-issues.rst | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-)