From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: prepare security process for vulnerabilities
Date: Tue, 07 May 2019 21:09:54 +0200 [thread overview]
Message-ID: <33157478.kEJyq2cdqh@xps> (raw)
In-Reply-To: <20190507120651.6283bd0c@hermes.lan>
07/05/2019 21:06, Stephen Hemminger:
> Thomas Monjalon <thomas@monjalon.net> wrote:
>
> > In case a vulnerability is discovered, the process to follow
> > is described in this document.
[...]
> Maybe there should be a keysigning at the DPDK summit
Yes it is must for using GPG in the security process.
next prev parent reply other threads:[~2019-05-07 19:09 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 [this message]
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=33157478.kEJyq2cdqh@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=techboard@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).