From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: prepare security process for vulnerabilities
Date: Tue, 7 May 2019 12:06:51 -0700 [thread overview]
Message-ID: <20190507120651.6283bd0c@hermes.lan> (raw)
Message-ID: <20190507190651.qpKJRN84i3xZhUGuPk79PcJZ2UBHrL43qMlAfJNowJU@z> (raw)
In-Reply-To: <20190507160231.18551-1-thomas@monjalon.net>
On Tue, 7 May 2019 18:02:31 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> In case a vulnerability is discovered, the process to follow
> is described in this document.
> It has been inspired by the process of some referenced projects
> and with the help of experts from Intel, RedHat, Mellanox
> and the Linux Foundation.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Maybe there should be a keysigning at the DPDK summit
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2019-05-07 19:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:02 Thomas Monjalon
2019-05-07 16:02 ` Thomas Monjalon
2019-05-07 19:06 ` Stephen Hemminger [this message]
2019-05-07 19:06 ` Stephen Hemminger
2019-05-07 19:09 ` Thomas Monjalon
2019-05-07 19:09 ` Thomas Monjalon
2019-05-07 22:38 ` Luca Boccassi
2019-05-07 22:38 ` Luca Boccassi
2019-05-08 8:09 ` Thomas Monjalon
2019-05-08 8:09 ` Thomas Monjalon
2019-05-13 20:49 ` Thomas Monjalon
2019-05-13 20:49 ` 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=20190507120651.6283bd0c@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
/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).