Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response

2023-06-15 Thread Stephen Hemminger
On Thu, 25 Feb 2021 14:14:29 + Ferruh Yigit 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 >

Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response

2023-03-31 Thread Thomas Monjalon
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 c

Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response

2021-02-25 Thread Ferruh Yigit
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 iss

Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response

2021-02-02 Thread Ferruh Yigit
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 report

[dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response

2021-01-24 Thread 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 p