From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, John McNamara <john.mcnamara@intel.com>
Subject: Re: [dpdk-web] [PATCH] clarify security action
Date: Tue, 25 Jun 2019 15:36:38 +0200 [thread overview]
Message-ID: <0aea9cbf-4d7f-517f-3014-9da8824176d3@redhat.com> (raw)
In-Reply-To: <20190617160402.6770-1-ferruh.yigit@intel.com>
On 6/17/19 6:04 PM, Ferruh Yigit wrote:
> Add a note to not use Bugzilla but report via email to security@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> content/security/_index.md | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/content/security/_index.md b/content/security/_index.md
> index a6927fc..3c1ad82 100644
> --- a/content/security/_index.md
> +++ b/content/security/_index.md
> @@ -5,8 +5,10 @@ weight = "9"
>
> ## Vulnerability Management
> ---
> -If a vulnerability is found in DPDK,
> -it must be reported, analyzed, fixed and disclosed according to the
> +If a vulnerability is found in DPDK, please do not use Bugzilla for reporting security issues.
> +Instead, send GPG-encrypted emails to [security@dpdk.org](mailto:security@dpdk.org). We will respond promptly to begin coordinating a fix and disclosure.
> +
> +Security issues must be reported, analyzed, fixed and disclosed according to the
> [vulnerability management process](//doc.dpdk.org/guides/contributing/vulnerability.html).
>
> ## Contact
>
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
next prev parent reply other threads:[~2019-06-25 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 16:04 Ferruh Yigit
2019-06-25 13:36 ` Maxime Coquelin [this message]
2019-06-25 13:46 ` Thomas Monjalon
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=0aea9cbf-4d7f-517f-3014-9da8824176d3@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).