From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 8EADA374C; Wed, 8 May 2019 10:09:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CD5D120CB1; Wed, 8 May 2019 04:09:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 08 May 2019 04:09:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=9AcT6XYiJHgkKAU1FVwVlqtYIzg4F9YmJL6vQnBJlQg=; b=L8mfiBcW+J+J SCEZFdAn8mlRTTMcTGK4pRHtSbvqyDnKqVvOg7EUbcDTqhyk5ydFjDDauUqClbvs O7OiUANRNxRTZcVpDqSKn40pmdFyj+GPldH39EtNPbPbLUcnp91ug5h37KtBEt5q C+LqzEliCkmG5icSfILUfMGsmSSUHFk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=9AcT6XYiJHgkKAU1FVwVlqtYIzg4F9YmJL6vQnBJl Qg=; b=b1A/tymztRVz+1PuMsytUw1nFmzZ4eKwlPHnjXrwLe497P4wAV6r7Qphk gxuyyg1y6t4xOlq2QWE+4h9f0+g9xPH6chbe41vMNh2NtxhNcyXA8Zjnq9mVO1HV c5Su9ND9Ll0qpmBajrrTjGS6dp0NVZA7cc6sdimRiNgHubLMEr59Ql1yZGdvAAVW oHgcbbwlKTwXSNZ4pqB6u85Uu8QijOXh5OAS9O/eobFvH2vxvrl9rfeej3nePtsg MKkDjjMjHWDkpECo1xk8Dltky9woqrpvwgSAbH35GxhaNUhxO+DMgOj5hs3wK1kG tsbR20Kd1FjjIjFT7RJHGTpo+OlZA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkedvgddvlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffoh hmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvddtfedrudekgeenucfr rghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenuc evlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 40B3010378; Wed, 8 May 2019 04:09:14 -0400 (EDT) From: Thomas Monjalon To: Luca Boccassi Cc: dev@dpdk.org, techboard@dpdk.org, Maxime Coquelin , Ferruh Yigit Date: Wed, 08 May 2019 10:09:12 +0200 Message-ID: <4374376.Bm3AYDqGPI@xps> In-Reply-To: <03d2500c1c55d1cd9c87eaf3f15ab1c9125251b3.camel@debian.org> References: <20190507160231.18551-1-thomas@monjalon.net> <03d2500c1c55d1cd9c87eaf3f15ab1c9125251b3.camel@debian.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: prepare security process for vulnerabilities X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2019 08:09:16 -0000 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id E54C1A0096 for ; Wed, 8 May 2019 10:09:17 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B84503772; Wed, 8 May 2019 10:09:17 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 8EADA374C; Wed, 8 May 2019 10:09:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CD5D120CB1; Wed, 8 May 2019 04:09:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 08 May 2019 04:09:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=9AcT6XYiJHgkKAU1FVwVlqtYIzg4F9YmJL6vQnBJlQg=; b=L8mfiBcW+J+J SCEZFdAn8mlRTTMcTGK4pRHtSbvqyDnKqVvOg7EUbcDTqhyk5ydFjDDauUqClbvs O7OiUANRNxRTZcVpDqSKn40pmdFyj+GPldH39EtNPbPbLUcnp91ug5h37KtBEt5q C+LqzEliCkmG5icSfILUfMGsmSSUHFk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=9AcT6XYiJHgkKAU1FVwVlqtYIzg4F9YmJL6vQnBJl Qg=; b=b1A/tymztRVz+1PuMsytUw1nFmzZ4eKwlPHnjXrwLe497P4wAV6r7Qphk gxuyyg1y6t4xOlq2QWE+4h9f0+g9xPH6chbe41vMNh2NtxhNcyXA8Zjnq9mVO1HV c5Su9ND9Ll0qpmBajrrTjGS6dp0NVZA7cc6sdimRiNgHubLMEr59Ql1yZGdvAAVW oHgcbbwlKTwXSNZ4pqB6u85Uu8QijOXh5OAS9O/eobFvH2vxvrl9rfeej3nePtsg MKkDjjMjHWDkpECo1xk8Dltky9woqrpvwgSAbH35GxhaNUhxO+DMgOj5hs3wK1kG tsbR20Kd1FjjIjFT7RJHGTpo+OlZA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkedvgddvlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucffoh hmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvddtfedrudekgeenucfr rghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthenuc evlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 40B3010378; Wed, 8 May 2019 04:09:14 -0400 (EDT) From: Thomas Monjalon To: Luca Boccassi Cc: dev@dpdk.org, techboard@dpdk.org, Maxime Coquelin , Ferruh Yigit Date: Wed, 08 May 2019 10:09:12 +0200 Message-ID: <4374376.Bm3AYDqGPI@xps> In-Reply-To: <03d2500c1c55d1cd9c87eaf3f15ab1c9125251b3.camel@debian.org> References: <20190507160231.18551-1-thomas@monjalon.net> <03d2500c1c55d1cd9c87eaf3f15ab1c9125251b3.camel@debian.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] doc: prepare security process for vulnerabilities X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190508080912.sLz5BrtbS06hAYNl_aug6HpTWHfJJlu5bFy2ZZQ0J2I@z> 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