doc: clarify disclosure time slot when no response
PATCH 1/1 doc: clarify disclosure time slot when no response
Sometimes security team won't send confirmation mail back to reporter in three business days. This mean reported vulnerability is either low severity or not a real vulnerability. Reporter should assume that the issue need shortest embargo. After that reporter can submit it through normal bugzilla process or send out fix patch to public.
doc/guides/contributing/vulnerability.rst +5 -0
@@ -99,6 +99,11 @@ Following information must be included in the mail: * Reporter credit * Bug ID (empty and restricted for future reference) +If no confirmation mail send back to reporter in this period, thus mean security +team take this vulnerability as low severity. Furthermore shortest embargo **two weeks** +is required for it. Reporter can sumbit the bug through normal process or send +out patch to public. + CVE Request -----------
Signature · 1 line
2.17.1
Quoted 14 lines · Marvin Liu
Sometimes security team won't send confirmation mail back to reporter in three business days. This mean reported vulnerability is either low severity or not a real vulnerability. Reporter should assume that the issue need shortest embargo. After that reporter can submit it through normal bugzilla process or send out fix patch to public.
Signed-off-by Marvin Liu <[email protected]>Signed-off-by Qian Xu <[email protected]>doc/guides/contributing/vulnerability.rst +0
-0
doc/guides/contributing/vulnerability.rst Following information must be included in the mail: · line 106
Quoted 8 lines
doc/guides/contributing/vulnerability.rst +5
-0@@ -99,6 +99,11 @@ Following information must be included in the mail: * Reporter credit * Bug ID (empty and restricted for future reference) +If no confirmation mail send back to reporter in this period, thus mean security +team take this vulnerability as low severity. Furthermore shortest embargo **two weeks** +is required for it. Reporter can sumbit the bug through normal process or send +out patch to public. +
Agree to not block the fixes, it is defeating the purpose to have a vulnerability process.
Quoted 10 lines · Ferruh Yigit
Quoted 9 lines · Marvin Liu
Sometimes security team won't send confirmation mail back to reporter in three business days. This mean reported vulnerability is either low severity or not a real vulnerability. Reporter should assume that the issue need shortest embargo. After that reporter can submit it through normal bugzilla process or send out fix patch to public.
Signed-off-by Marvin Liu <[email protected]>Signed-off-by Qian Xu <[email protected]>
Quoted 15 lines
doc/guides/contributing/vulnerability.rst Following information must be included in the mail: · line 106
Quoted 13 lines
doc/guides/contributing/vulnerability.rst +5
-0@@ -99,6 +99,11 @@ Following information must be included in the mail: * Reporter credit * Bug ID (empty and restricted for future reference) +If no confirmation mail send back to reporter in this period, thus mean security +team take this vulnerability as low severity. Furthermore shortest embargo **two weeks** +is required for it. Reporter can sumbit the bug through normal process or send +out patch to public. +Agree to not block the fixes, it is defeating the purpose to have a vulnerability process.
The patch is out for a while and there is no objection so far, I suggest just keep continue with the fixes stuck in the process.
Quoted 29 lines · On Thu, 25 Feb 2021 14:14:29 +0000 Ferruh Yigit <[email protected]> wrote:
Quoted 19 lines · Ferruh Yigit
Quoted 18 lines · Marvin Liu
Sometimes security team won't send confirmation mail back to reporter in three business days. This mean reported vulnerability is either low severity or not a real vulnerability. Reporter should assume that the issue need shortest embargo. After that reporter can submit it through normal bugzilla process or send out fix patch to public.
Signed-off-by Marvin Liu <[email protected]>Signed-off-by Qian Xu <[email protected]>doc/guides/contributing/vulnerability.rst +1
-0@@ -99,6 +99,11 @@ Following information must be included in the mail: * Reporter credit * Bug ID (empty and restricted for future reference) +If no confirmation mail send back to reporter in this period, thus mean securityQuoted 8 lines
doc/guides/contributing/vulnerability.rst Following information must be included in the mail: · line 106
Quoted 5 lines
doc/guides/contributing/vulnerability.rst +4
-0+team take this vulnerability as low severity. Furthermore shortest embargo **two weeks** +is required for it. Reporter can sumbit the bug through normal process or send +out patch to public. +Agree to not block the fixes, it is defeating the purpose to have a vulnerability process.
Quoted 2 lines
The patch is out for a while and there is no objection so far, I suggest just keep continue with the fixes stuck in the process.
Marking this patch as rejected. Open to future wording/process changes here but it didn't seem necessary and no consensus in several years
25/01/2021 02:57, Marvin Liu:
Quoted 14 lines
Sometimes security team won't send confirmation mail back to reporter in three business days. This mean reported vulnerability is either low severity or not a real vulnerability. Reporter should assume that the issue need shortest embargo. After that reporter can submit it through normal bugzilla process or send out fix patch to public.
Signed-off-by Marvin Liu <[email protected]>Signed-off-by Qian Xu <[email protected]>doc/guides/contributing/vulnerability.rst +0
-0
doc/guides/contributing/vulnerability.rst Following information must be included in the mail: · line 104
Quoted 6 lines
doc/guides/contributing/vulnerability.rst +3
-0@@ -99,6 +99,11 @@ Following information must be included in the mail: * Reporter credit * Bug ID (empty and restricted for future reference) +If no confirmation mail send back to reporter in this period, thus mean security +team take this vulnerability as low severity. Furthermore shortest embargo **two weeks** +is required for it. Reporter can sumbit the bug through normal process or send
sumbit -> submit
doc/guides/contributing/vulnerability.rst Following information must be included in the mail: · line 105
Quoted 1 line
doc/guides/contributing/vulnerability.rst +1
-0+out patch to public.
Do we agree on the principle?
Does it require a bit of rewriting?
Quoted 11 lines · On Fri, 31 Mar 2023 12:38:23 +0200 Thomas Monjalon <[email protected]> wrote:
doc/guides/contributing/vulnerability.rst Following information must be included in the mail: · line 104
Quoted 4 lines
doc/guides/contributing/vulnerability.rst +3
-0+If no confirmation mail send back to reporter in this period, thus mean security +team take this vulnerability as low severity. Furthermore shortest embargo **two weeks** +is required for it. Reporter can sumbit the bug through normal process or sendsumbit -> submit
Quoted 1 line
+out patch to public.
Do we agree on the principle?
Does it require a bit of rewriting?
LGTM