07/05/2019 18:02, Thomas Monjalon:
> 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-of
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,
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 Fou
07/05/2019 21:06, Stephen Hemminger:
> Thomas Monjalon 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.
On Tue, 7 May 2019 18:02:31 +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 F
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
Signed-off-by: Maxime Coqu
6 matches
Mail list logo
