From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6A42C432BE for ; Wed, 18 Aug 2021 02:09:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 88B8861059 for ; Wed, 18 Aug 2021 02:09:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236053AbhHRCK3 (ORCPT ); Tue, 17 Aug 2021 22:10:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:49628 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233380AbhHRCK0 (ORCPT ); Tue, 17 Aug 2021 22:10:26 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6AC4F60F5E; Wed, 18 Aug 2021 02:09:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1629252592; bh=B15pn2XunpVBloy8qLk8GOdp/fRGBs/dMCBl1c1wvW8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HuBUUoZEtHR8q3eIHhlcYOMaxVYN9EtN5/AnsOeRV7mlH1f3r4Nz5Ka5dQpaVrr7f AzEuFy1vbDUheHR+mm3qjkfrCzg9oclx9Sbc2tfkAlxLEFIUnPkRRhMUpwipNFBN3B y751zJkymZ/G6drWdcxb+8ixCgP29n0XLQIX1azSirCxo7Z/oDqBRKWV3xTgNFK6dk VCkItm1/os96sMi5D3/7K5HqrOD50nuI00r6bWq/s1XyqhWnIRWW8NZjhw5PvNg7i6 GbDirjDIVLcodJ3YerbdyN/5Y436Zu3NzcajsGgBRXWkhw3TPkYbfRwn1rysZJyN4P 9N6z4Z09XR3RQ== Date: Wed, 18 Aug 2021 05:09:50 +0300 From: Jarkko Sakkinen To: Mimi Zohar Cc: Ahmad Fatoum , Eric Biggers , "Theodore Y. Ts'o" , Jaegeuk Kim , kernel@pengutronix.de, James Morris , "Serge E. Hallyn" , James Bottomley , Sumit Garg , David Howells , linux-fscrypt@vger.kernel.org, linux-crypto@vger.kernel.org, linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] fscrypt: support trusted keys Message-ID: <20210818020950.GA23184@iki.fi> References: <20210810212140.sdq5dq2wy5uaj7h7@kernel.org> <20210811001743.ofzkwdwa6rcjsf4d@kernel.org> <0e69a0aa394dd20347b06ae4e700aa17d52583ef.camel@linux.ibm.com> <285cb263d9c1c16f3918c98dd36074ef16568e6d.camel@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, Aug 17, 2021 at 10:24:44AM -0400, Mimi Zohar wrote: > On Tue, 2021-08-17 at 16:13 +0200, Ahmad Fatoum wrote: > > On 17.08.21 15:55, Mimi Zohar wrote: > > > I have no opinion as to whether this is/isn't a valid usecase. > > > > So you'd be fine with merging trusted key support as is and leave encrypted > > key support to someone who has a valid use case and wants to argue > > in its favor? > > That decision as to whether it makes sense to support trusted keys > directly, based on the new trust sources, is a decision left up to the > maintainer(s) of the new usecase and the new trust sources maintainer > Jarkko. I'm fine with "direct", as long as also "indirect" is supported. /Jarkko