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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,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 7A558C43216 for ; Wed, 18 Aug 2021 04:53:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6559A6108D for ; Wed, 18 Aug 2021 04:53:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237815AbhHREy0 (ORCPT ); Wed, 18 Aug 2021 00:54:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56034 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237769AbhHREyW (ORCPT ); Wed, 18 Aug 2021 00:54:22 -0400 Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 95613C0613D9 for ; Tue, 17 Aug 2021 21:53:48 -0700 (PDT) Received: by mail-lf1-x131.google.com with SMTP id z2so1951244lft.1 for ; Tue, 17 Aug 2021 21:53:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6K3+N3LYrTw7honvxshLdEmV5XuzaI7RIQ6phcsSuqs=; b=PMOjOlGYA8htOgmQ85BkiqbjuX25YAO64oKb0lJyjDOWObdytQ/NuwquW22Q6SsImv ONkEw7ASyg72uJzDI00etWlR005j4RuaerlWqgYid/lBgJhfWqroVyTGyfm+10YWt1RE IhOCuqLYRFKOWzOs+njufqJUTl6tDAEAxqofqPejffXiZ4kjFF/tsFlgzoloc5SeeNAv 0EDtsmjT3KKbL2ryi8x4kTrCHl2l/RoOKeCnfj3yHwIxajrdmN+a3cmr/MKC+Q0PPqby E7/AheMP1fCmnoSgjNMidl0ZorUNVAJktffOd7pmG++IaUrcvu3IW2pparCgKxal7wWw +MDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6K3+N3LYrTw7honvxshLdEmV5XuzaI7RIQ6phcsSuqs=; b=fhiIveLKobaYp8YJbCbYpVwbkm9npCcYYeYtVGvkb1AVjjCCRDHh2pv7uxM8mvpX6r vo8snnjMmoHFK+/grt0kOla81pQvzRcq6vEwDSXpOJweugmNZpGYNusDOJ83vf20Vuxw 2wGIBOIjjOFjud5YTQAOI/bKYuG+bwRtM49fYUbjwQt9iSkWVfjYDJeXRHCvy+wC2Lcl JGleJrcuQ/o+UAyUPry3MFoaVY1ST2Me2Yc2hjT9X9eTt0XlES4vv/+xbcIud2dhxFln YTfcpTDhyuzQru0z2imYYUDMWFcZWOh1HwABRYV0/Kab8aoLniXayGjVpS+o147eFqlJ CFfA== X-Gm-Message-State: AOAM532VT9eEYWk2TAvxk+snkDIHn69Ulfci9A/9iVgjx53OBgvvlxwK ykdT2yGUME/izgPU1BAl/+2B4XmZZk613mFQHZKRzA== X-Google-Smtp-Source: ABdhPJzzVy3i/YL271hD0LPO7hSavfFPRoKZqMe7jV9Gv3YssPhhOr2s5XndnaUsuIYHNkYUWODkRVaV8/1DYvrjlH4= X-Received: by 2002:a05:6512:c24:: with SMTP id z36mr5140198lfu.194.1629262426962; Tue, 17 Aug 2021 21:53:46 -0700 (PDT) MIME-Version: 1.0 References: <20210806150928.27857-1-a.fatoum@pengutronix.de> <20210809094408.4iqwsx77u64usfx6@kernel.org> <20210810180636.vqwaeftv7alsodgn@kernel.org> <20210810212140.sdq5dq2wy5uaj7h7@kernel.org> <20210811001743.ofzkwdwa6rcjsf4d@kernel.org> <0e69a0aa394dd20347b06ae4e700aa17d52583ef.camel@linux.ibm.com> <285cb263d9c1c16f3918c98dd36074ef16568e6d.camel@linux.ibm.com> In-Reply-To: From: Sumit Garg Date: Wed, 18 Aug 2021 10:23:35 +0530 Message-ID: Subject: Re: [PATCH v2] fscrypt: support trusted keys To: Mimi Zohar Cc: Ahmad Fatoum , Eric Biggers , Jarkko Sakkinen , "Theodore Y. Ts'o" , Jaegeuk Kim , kernel , James Morris , "Serge E. Hallyn" , James Bottomley , David Howells , linux-fscrypt@vger.kernel.org, "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , linux-integrity , "open list:SECURITY SUBSYSTEM" , "open list:ASYMMETRIC KEYS" , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 17 Aug 2021 at 19:54, 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 would be in favor of supporting the use of trusted keys directly when it comes to TEE as a trust source. -Sumit > thanks, > > Mimi >