DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, web@dpdk.org
Cc: maxime.coquelin@redhat.com
Subject: Re: [dpdk-web] [PATCH] add page about security
Date: Tue, 21 May 2019 18:38:05 +0100	[thread overview]
Message-ID: <6068ae2f-8ac1-0d47-d467-1591ded7375e@intel.com> (raw)
In-Reply-To: <20190520161819.3711-1-thomas@monjalon.net>

On 5/20/2019 5:18 PM, Thomas Monjalon wrote:
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  content/security/_index.md  | 19 +++++++++++++++++++
>  content/techboard/_index.md |  2 +-
>  content/training/_index.md  |  2 +-
>  3 files changed, 21 insertions(+), 2 deletions(-)
>  create mode 100644 content/security/_index.md
> 
> diff --git a/content/security/_index.md b/content/security/_index.md
> new file mode 100644
> index 0000000..a6927fc
> --- /dev/null
> +++ b/content/security/_index.md
> @@ -0,0 +1,19 @@
> ++++
> +title = "Security"
> +weight = "9"
> ++++
> +
> +## Vulnerability Management
> +---
> +If a vulnerability is found in DPDK,
> +it must be reported, analyzed, fixed and disclosed according to the
> +[vulnerability management process](//doc.dpdk.org/guides/contributing/vulnerability.html).
> +
> +## Contact
> +---
> +The Security Team can be reached at [security@dpdk.org](mailto:security@dpdk.org).
> +
> +For any security report, the message should be encrypted with the following GPG keys:
> +
> +- `F933EB43DF13611F` - *Ferruh Yigit*

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>


  parent reply	other threads:[~2019-05-21 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 16:18 Thomas Monjalon
2019-05-20 17:12 ` Maxime Coquelin
2019-05-21 17:38 ` Ferruh Yigit [this message]
2019-05-21 17:40   ` 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=6068ae2f-8ac1-0d47-d467-1591ded7375e@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=web@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).