* [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response
@ 2021-01-25 1:57 Marvin Liu
2021-02-02 11:28 ` Ferruh Yigit
2023-03-31 10:38 ` Thomas Monjalon
0 siblings, 2 replies; 6+ messages in thread
From: Marvin Liu @ 2021-01-25 1:57 UTC (permalink / raw)
To: ferruh.yigit, stephen, thomas, maxime.coquelin, qian.q.xu; +Cc: dev, 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 <yong.liu@intel.com>
Signed-off-by: Qian Xu <qian.q.xu@intel.com>
diff --git a/doc/guides/contributing/vulnerability.rst b/doc/guides/contributing/vulnerability.rst
index b6300252ad..cda814fa69 100644
--- a/doc/guides/contributing/vulnerability.rst
+++ b/doc/guides/contributing/vulnerability.rst
@@ -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
-----------
--
2.17.1
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response
2021-01-25 1:57 [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response Marvin Liu
@ 2021-02-02 11:28 ` Ferruh Yigit
2021-02-25 14:14 ` Ferruh Yigit
2023-03-31 10:38 ` Thomas Monjalon
1 sibling, 1 reply; 6+ messages in thread
From: Ferruh Yigit @ 2021-02-02 11:28 UTC (permalink / raw)
To: Marvin Liu, stephen, thomas, maxime.coquelin, qian.q.xu; +Cc: dev
On 1/25/2021 1:57 AM, Marvin Liu wrote:
> 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 <yong.liu@intel.com>
> Signed-off-by: Qian Xu <qian.q.xu@intel.com>
>
> diff --git a/doc/guides/contributing/vulnerability.rst b/doc/guides/contributing/vulnerability.rst
> index b6300252ad..cda814fa69 100644
> --- a/doc/guides/contributing/vulnerability.rst
> +++ b/doc/guides/contributing/vulnerability.rst
> @@ -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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response
2021-02-02 11:28 ` Ferruh Yigit
@ 2021-02-25 14:14 ` Ferruh Yigit
2023-06-15 16:17 ` Stephen Hemminger
0 siblings, 1 reply; 6+ messages in thread
From: Ferruh Yigit @ 2021-02-25 14:14 UTC (permalink / raw)
To: Marvin Liu, stephen, thomas, maxime.coquelin, qian.q.xu; +Cc: dev
On 2/2/2021 11:28 AM, Ferruh Yigit wrote:
> On 1/25/2021 1:57 AM, Marvin Liu wrote:
>> 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 <yong.liu@intel.com>
>> Signed-off-by: Qian Xu <qian.q.xu@intel.com>
>>
>> diff --git a/doc/guides/contributing/vulnerability.rst
>> b/doc/guides/contributing/vulnerability.rst
>> index b6300252ad..cda814fa69 100644
>> --- a/doc/guides/contributing/vulnerability.rst
>> +++ b/doc/guides/contributing/vulnerability.rst
>> @@ -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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response
2021-01-25 1:57 [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response Marvin Liu
2021-02-02 11:28 ` Ferruh Yigit
@ 2023-03-31 10:38 ` Thomas Monjalon
2023-03-31 15:31 ` Stephen Hemminger
1 sibling, 1 reply; 6+ messages in thread
From: Thomas Monjalon @ 2023-03-31 10:38 UTC (permalink / raw)
To: ferruh.yigit, stephen, maxime.coquelin
Cc: qian.q.xu, dev, Marvin Liu, david.marchand, cheng.jiang
25/01/2021 02:57, 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 <yong.liu@intel.com>
> Signed-off-by: Qian Xu <qian.q.xu@intel.com>
>
> diff --git a/doc/guides/contributing/vulnerability.rst b/doc/guides/contributing/vulnerability.rst
> index b6300252ad..cda814fa69 100644
> --- a/doc/guides/contributing/vulnerability.rst
> +++ b/doc/guides/contributing/vulnerability.rst
> @@ -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
> +out patch to public.
Do we agree on the principle?
Does it require a bit of rewriting?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response
2023-03-31 10:38 ` Thomas Monjalon
@ 2023-03-31 15:31 ` Stephen Hemminger
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Hemminger @ 2023-03-31 15:31 UTC (permalink / raw)
To: Thomas Monjalon
Cc: ferruh.yigit, maxime.coquelin, qian.q.xu, dev, Marvin Liu,
david.marchand, cheng.jiang
On Fri, 31 Mar 2023 12:38:23 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > +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
>
> > +out patch to public.
>
> Do we agree on the principle?
> Does it require a bit of rewriting?
LGTM
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response
2021-02-25 14:14 ` Ferruh Yigit
@ 2023-06-15 16:17 ` Stephen Hemminger
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Hemminger @ 2023-06-15 16:17 UTC (permalink / raw)
To: Ferruh Yigit; +Cc: Marvin Liu, thomas, maxime.coquelin, qian.q.xu, dev
On Thu, 25 Feb 2021 14:14:29 +0000
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 2/2/2021 11:28 AM, Ferruh Yigit wrote:
> > On 1/25/2021 1:57 AM, Marvin Liu wrote:
> >> 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 <yong.liu@intel.com>
> >> Signed-off-by: Qian Xu <qian.q.xu@intel.com>
> >>
> >> diff --git a/doc/guides/contributing/vulnerability.rst
> >> b/doc/guides/contributing/vulnerability.rst
> >> index b6300252ad..cda814fa69 100644
> >> --- a/doc/guides/contributing/vulnerability.rst
> >> +++ b/doc/guides/contributing/vulnerability.rst
> >> @@ -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.
Marking this patch as rejected. Open to future wording/process changes here
but it didn't seem necessary and no consensus in several years
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-06-15 16:17 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-25 1:57 [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response Marvin Liu
2021-02-02 11:28 ` Ferruh Yigit
2021-02-25 14:14 ` Ferruh Yigit
2023-06-15 16:17 ` Stephen Hemminger
2023-03-31 10:38 ` Thomas Monjalon
2023-03-31 15:31 ` Stephen Hemminger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).