From: Luca Boccassi <bluca@debian.org>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Cc: techboard@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: prepare security process for vulnerabilities
Date: Tue, 07 May 2019 23:38:57 +0100 [thread overview]
Message-ID: <03d2500c1c55d1cd9c87eaf3f15ab1c9125251b3.camel@debian.org> (raw)
Message-ID: <20190507223857.mHnnO9IE9J5_ImWLmHbZ115BlUfo0Rimk-bbIO0v-3k@z> (raw)
In-Reply-To: <20190507160231.18551-1-thomas@monjalon.net>
On Tue, 2019-05-07 at 18:02 +0200, Thomas Monjalon 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
> >
> ---
> doc/guides/contributing/index.rst | 1 +
> doc/guides/contributing/vulnerability.rst | 316
> ++++++++++++++++++++++
> 2 files changed, 317 insertions(+)
> create mode 100644 doc/guides/contributing/vulnerability.rst
I think at least the fingerprint of the GPG key to encrypt to, if a
link to the whole public key given the page is served over https,
should be on the page.
Other than that, good stuff!
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-05-07 22:39 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
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 [this message]
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=03d2500c1c55d1cd9c87eaf3f15ab1c9125251b3.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=maxime.coquelin@redhat.com \
--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).