DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Marvin Liu <yong.liu@intel.com>,
	stephen@networkplumber.org, thomas@monjalon.net,
	maxime.coquelin@redhat.com, qian.q.xu@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: clarify disclosure time slot when no response
Date: Tue, 2 Feb 2021 11:28:09 +0000	[thread overview]
Message-ID: <67154af1-a00e-2572-5ae9-75d965ab3169@intel.com> (raw)
In-Reply-To: <20210125015736.7555-1-yong.liu@intel.com>

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.

  reply	other threads:[~2021-02-02 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25  1:57 Marvin Liu
2021-02-02 11:28 ` Ferruh Yigit [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=67154af1-a00e-2572-5ae9-75d965ab3169@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=yong.liu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).