From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id EC8E828FD; Tue, 7 May 2019 21:09:57 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 89E6F23944; Tue, 7 May 2019 15:09:57 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 07 May 2019 15:09:57 -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=OssAbfcVlD7NYjjxvukPuGXDUaIbrtQh5pr0qD5E/r0=; b=d98DClx0Lc9J iDhxXjvQi/2B8qKYZybMpRpD4zX6zMyRgSgIDJCnvyq/7RCPXrBJxCPTBOOlAfED QQBOxOkSNSjxvPM68V1cc0yKP17TJt7iobdO734bNGqumAI03Tvq/fezGQbcmKLj yrcm5JkRa/hqZJSmhf2WskkRGVC+5Ig= 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=OssAbfcVlD7NYjjxvukPuGXDUaIbrtQh5pr0qD5E/ r0=; b=UOITqQBLxd7VwC8cttGbm37oClMudy7w1UpLI9EkX0KZR4LaHiuT1RAdK al68+7f3w3TW1Ww2St1Y5uFNSarFziIFg0O+cGSj8hXOKuWiUcnGjP5DqCCVL/Kt FYPdKvXNbAeg7+VPpxAg/ARs4Kfps2TyS++TzdKi0umPkN/kZgyKi0xUAKEj39fg yg292E8hBB7gAQpaTpI5WEFutmgHG4w5MlJriyX9ooZdy+JGxxi6u/nmqxRG/qeg ELJI2Z7u7HvV2ycAb2qWvCQqOoK0lhFJ5C6az8qEpRuwitsL9IRmnRI1qxwvZC7J DDaKU3cWMz7wKQ/Q/s3Oc8i3glOcw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkedtgddufeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 6EAD2103C8; Tue, 7 May 2019 15:09:56 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, techboard@dpdk.org Date: Tue, 07 May 2019 21:09:54 +0200 Message-ID: <33157478.kEJyq2cdqh@xps> In-Reply-To: <20190507120651.6283bd0c@hermes.lan> References: <20190507160231.18551-1-thomas@monjalon.net> <20190507120651.6283bd0c@hermes.lan> 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: Tue, 07 May 2019 19:09:58 -0000 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. 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 6FEFBA0096 for ; Tue, 7 May 2019 21:10:00 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8E1C4293B; Tue, 7 May 2019 21:09:59 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id EC8E828FD; Tue, 7 May 2019 21:09:57 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 89E6F23944; Tue, 7 May 2019 15:09:57 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 07 May 2019 15:09:57 -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=OssAbfcVlD7NYjjxvukPuGXDUaIbrtQh5pr0qD5E/r0=; b=d98DClx0Lc9J iDhxXjvQi/2B8qKYZybMpRpD4zX6zMyRgSgIDJCnvyq/7RCPXrBJxCPTBOOlAfED QQBOxOkSNSjxvPM68V1cc0yKP17TJt7iobdO734bNGqumAI03Tvq/fezGQbcmKLj yrcm5JkRa/hqZJSmhf2WskkRGVC+5Ig= 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=OssAbfcVlD7NYjjxvukPuGXDUaIbrtQh5pr0qD5E/ r0=; b=UOITqQBLxd7VwC8cttGbm37oClMudy7w1UpLI9EkX0KZR4LaHiuT1RAdK al68+7f3w3TW1Ww2St1Y5uFNSarFziIFg0O+cGSj8hXOKuWiUcnGjP5DqCCVL/Kt FYPdKvXNbAeg7+VPpxAg/ARs4Kfps2TyS++TzdKi0umPkN/kZgyKi0xUAKEj39fg yg292E8hBB7gAQpaTpI5WEFutmgHG4w5MlJriyX9ooZdy+JGxxi6u/nmqxRG/qeg ELJI2Z7u7HvV2ycAb2qWvCQqOoK0lhFJ5C6az8qEpRuwitsL9IRmnRI1qxwvZC7J DDaKU3cWMz7wKQ/Q/s3Oc8i3glOcw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkedtgddufeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 6EAD2103C8; Tue, 7 May 2019 15:09:56 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, techboard@dpdk.org Date: Tue, 07 May 2019 21:09:54 +0200 Message-ID: <33157478.kEJyq2cdqh@xps> In-Reply-To: <20190507120651.6283bd0c@hermes.lan> References: <20190507160231.18551-1-thomas@monjalon.net> <20190507120651.6283bd0c@hermes.lan> 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: <20190507190954.Ld529DGSXUE5aD_Ks7IGR_4cspJaIVQucjr3COaQ1Lg@z> 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.