doc: add oss-security to the security process
PATCH 1/1 doc: add oss-security to the security process
From: Luca Boccassi <[email protected]>
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.
---
As discussed at Userspace, we should include oss-security in the advanced private notice. This change has a brief explanation and a link to the process.
doc/guides/contributing/vulnerability.rst | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
doc/guides/contributing/vulnerability.rst +11 -2
@@ -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 `[email protected] <mailto:[email protected]>`_ +The `OSS security private mailing list mailto:[email protected]>` 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, describind 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 protected] <mailto:[email protected]>`_ -as soon as the patches are pushed to the appropriate branches. +to `[email protected] <mailto:[email protected]>`_ and to `the public OSS-security +mailing list <mailto:[email protected]>` as soon as the patches +are pushed to the appropriate branches. Patches are then sent to `[email protected] <mailto:[email protected]>`_ and `[email protected] <mailto:[email protected]>`_ accordingly.
Signature · 1 line
2.20.1
PATCH v2 1/1 doc: add oss-security to the security process
From: Luca Boccassi <[email protected]>
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.
---
v1: As discussed at Userspace, we should include oss-security in the advanced
private notice. This change has a brief explanation and a link to the process.
v2: --signoff missing in v1, lost somewhere between brain and keyboard
doc/guides/contributing/vulnerability.rst | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
doc/guides/contributing/vulnerability.rst +11 -2
@@ -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 `[email protected] <mailto:[email protected]>`_ +The `OSS security private mailing list mailto:[email protected]>` 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, describind 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 protected] <mailto:[email protected]>`_ -as soon as the patches are pushed to the appropriate branches. +to `[email protected] <mailto:[email protected]>`_ and to `the public OSS-security +mailing list <mailto:[email protected]>` as soon as the patches +are pushed to the appropriate branches. Patches are then sent to `[email protected] <mailto:[email protected]>`_ and `[email protected] <mailto:[email protected]>`_ accordingly.
Signature · 1 line
2.20.1
Quoted 10 lines · On 9/21/19 4:52 PM, [email protected] wrote:
From: Luca Boccassi <[email protected]>
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 <[email protected]>
Quoted 8 lines
---
v1: As discussed at Userspace, we should include oss-security in the advanced
private notice. This change has a brief explanation and a link to the process.
v2: --signoff missing in v1, lost somewhere between brain and keyboarddoc/guides/contributing/vulnerability.rst | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
Thanks Luca, it's much appreciated.
Other than the typo reported below, it looks good to me:
Maxime
doc/guides/contributing/vulnerability.rst Downstream stakeholders (in `security-prerelease list · line 200
Quoted 13 lines
doc/guides/contributing/vulnerability.rst +4
-0@@ -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 `[email protected] <mailto:[email protected]>`_ +The `OSS security private mailing list mailto:[email protected]>` 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, describind the details of the
s/describind/describing/
Quoted 20 lines
doc/guides/contributing/vulnerability.rst +7
-2+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 protected] <mailto:[email protected]>`_ -as soon as the patches are pushed to the appropriate branches. +to `[email protected] <mailto:[email protected]>`_ and to `the public OSS-security +mailing list <mailto:[email protected]>` as soon as the patches +are pushed to the appropriate branches. Patches are then sent to `[email protected] <mailto:[email protected]>`_ and `[email protected] <mailto:[email protected]>`_ accordingly.
David Marchand
AppliedQuoted 37 lines · Maxime Coquelin
Quoted 10 lines · On 9/21/19 4:52 PM, [email protected] wrote:
From: Luca Boccassi <[email protected]>
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 <[email protected]>Quoted 8 lines
---
v1: As discussed at Userspace, we should include oss-security in the advanced
private notice. This change has a brief explanation and a link to the process.
v2: --signoff missing in v1, lost somewhere between brain and keyboarddoc/guides/contributing/vulnerability.rst | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)Thanks Luca, it's much appreciated.
Other than the typo reported below, it looks good to me:Reviewed-by Maxime Coquelin <[email protected]>Maxime
Quoted 9 lines
doc/guides/contributing/vulnerability.rst +0
-0@@ -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 `[email protected] <mailto:[email protected]>`_
Quoted 6 lines
doc/guides/contributing/vulnerability.rst Downstream stakeholders (in `security-prerelease list · line 200
Quoted 4 lines
doc/guides/contributing/vulnerability.rst +4
-0+The `OSS security private mailing list mailto:[email protected]>` 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, describind the details of thes/describind/describing/
Fixed while applying.
Quoted 18 lines
Quoted 18 lines
doc/guides/contributing/vulnerability.rst +7
-2+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 protected] <mailto:[email protected]>`_ -as soon as the patches are pushed to the appropriate branches. +to `[email protected] <mailto:[email protected]>`_ and to `the public OSS-security +mailing list <mailto:[email protected]>` as soon as the patches +are pushed to the appropriate branches.
Quoted 3 lines
doc/guides/contributing/vulnerability.rst Releases on Monday to Wednesday are preferred, so that system administrators · line 292
Quoted 3 lines
doc/guides/contributing/vulnerability.rst +0
-0Patches are then sent to `[email protected] <mailto:[email protected]>`_ and `[email protected] <mailto:[email protected]>`_ accordingly.
Applied, thanks.
Signature · 1 line
David Marchand