From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1F81CEFF for ; Sun, 23 Sep 2018 18:34:12 +0000 (UTC) Received: from imap.thunk.org (imap.thunk.org [74.207.234.97]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6CE50A8 for ; Sun, 23 Sep 2018 18:34:11 +0000 (UTC) Date: Sun, 23 Sep 2018 14:34:07 -0400 From: "Theodore Y. Ts'o" To: Jiri Kosina Message-ID: <20180923183407.GA2774@thunk.org> References: <20180922131640.pxjwukrckggxtg3s@mwanda> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: ksummit-discuss@lists.linuxfoundation.org, Dan Carpenter Subject: Re: [Ksummit-discuss] [TECH TOPIC] Security List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, Sep 23, 2018 at 03:20:22PM +0200, Jiri Kosina wrote: > 3) there simply is a need for CRD process for the kernel (which pretty > much by definition is not happening publicly). Currently, security@ > serves that purpose, so if you make that public, you have to > instantiate some other process to deal with CRDs. Can you expand the acronym "CRD". - Ted