|author||Luca Boccassi <firstname.lastname@example.org>||2019-09-21 16:52:42 +0200|
|committer||David Marchand <email@example.com>||2019-11-15 09:54:55 +0100|
doc: add oss-security to the security process
The OSS-security project functions as a single point of contact for pre-release, embargoed security notifications. Distributions and major vendors are subscribed to this private list, so that they can be warned in advance and schedule the work required to fix the vulnerability. List and link this process in the DPDK security process document. Signed-off-by: Luca Boccassi <firstname.lastname@example.org> Reviewed-by: Maxime Coquelin <email@example.com>
1 files changed, 11 insertions, 2 deletions
diff --git a/doc/guides/contributing/vulnerability.rst b/doc/guides/contributing/vulnerability.rst
index a4bef48..5484119 100644
@@ -194,6 +194,14 @@ Downstream stakeholders (in `security-prerelease list
* Major DPDK users, considered trustworthy by the technical board, who
have made the request to `firstname.lastname@example.org <mailto:email@example.com>`_
+The `OSS security private mailing list mailto:firstname.lastname@example.org>` will
+also be contacted one week before the end of the embargo, as indicated by `the
+OSS-security process <https://oss-security.openwall.org/wiki/mailing-lists/distros>`
+and using the PGP key listed on the same page, describing the details of the
+vulnerability and sharing the patch[es]. Distributions and major vendors follow
+this private mailing list, and it functions as a single point of contact for
+embargoed advance notices for open source projects.
The security advisory will be based on below template,
and will be sent signed with a security team's member GPG key.
@@ -276,8 +284,9 @@ Releases on Monday to Wednesday are preferred, so that system administrators
do not have to deal with security updates over the weekend.
The security advisory is posted
-to `email@example.com <mailto:firstname.lastname@example.org>`_
-as soon as the patches are pushed to the appropriate branches.
+to `email@example.com <mailto:firstname.lastname@example.org>`_ and to `the public OSS-security
+mailing list <mailto:email@example.com>` as soon as the patches
+are pushed to the appropriate branches.
Patches are then sent to `firstname.lastname@example.org <mailto:email@example.com>`_
and `firstname.lastname@example.org <mailto:email@example.com>`_ accordingly.