From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>
Cc: dev@dpdk.org, 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: Wed, 08 May 2019 10:09:12 +0200 [thread overview]
Message-ID: <4374376.Bm3AYDqGPI@xps> (raw)
In-Reply-To: <03d2500c1c55d1cd9c87eaf3f15ab1c9125251b3.camel@debian.org>
08/05/2019 00:38, Luca Boccassi:
> On Tue, 2019-05-07 at 18:02 +0200, Thomas Monjalon wrote:
> > 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.
I would like to avoid updating this doc (in all branches)
when a GPG key is added or changed.
That's why I provided a link to a web page, not created yet:
http://core.dpdk.org/doc/security#contact
next prev parent reply other threads:[~2019-05-08 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:02 [dpdk-dev] [PATCH] doc: prepare security process for vulnerabilities Thomas Monjalon
2019-05-07 19:06 ` Stephen Hemminger
2019-05-07 19:09 ` Thomas Monjalon
2019-05-07 22:38 ` Luca Boccassi
2019-05-08 8:09 ` Thomas Monjalon [this message]
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=4374376.Bm3AYDqGPI@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=maxime.coquelin@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.