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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 49DDEC742A8 for ; Fri, 12 Jul 2019 05:13:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1274B20863 for ; Fri, 12 Jul 2019 05:13:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="nYyYj4Td" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725974AbfGLFNv (ORCPT ); Fri, 12 Jul 2019 01:13:51 -0400 Received: from mail-lf1-f54.google.com ([209.85.167.54]:38406 "EHLO mail-lf1-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725948AbfGLFNu (ORCPT ); Fri, 12 Jul 2019 01:13:50 -0400 Received: by mail-lf1-f54.google.com with SMTP id h28so5575606lfj.5 for ; Thu, 11 Jul 2019 22:13:49 -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=h1l+yKMs5eoMYO2qnNQH2xVuYFvFDBbrlUII08j6+mA=; b=nYyYj4Td71VI953FAnyXurziweSCfNklLpK/20JzdgHfGVOtnzeWSnTD3QpkBj1m1j 0+XmP7aKHmB2tFrjhco2B+BLfXxMvapsbXEtTS75L9D50cT/Q2k5mi6/ZGUMADNYJ6M9 /wuGf83vcQk9fw1Hq2K8CgfhpnTk+MjsURGJYWwESfgUrX+cFxD0RX8+iLv9l+U1x+Ru +2L7b1HpO0WufLCNfWtO6u0yVL2VhFfuXVTpsxpQBt1N2FTYYnoKgiYAm9CTf7lQSH+D 7//dX24mOdjvvoS0Rie7FLIkW9l4pAywDy0IClhfcvZNIxXxJhwrw4/kcgHqvDlhqhCu WXTg== 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=h1l+yKMs5eoMYO2qnNQH2xVuYFvFDBbrlUII08j6+mA=; b=qZeSHYyCDEkzLSpQUN4j3TUd/twpNJj1UyBgddDjP5k7cgxJqOceAsCFRJIuMshDN8 Mw53NG8u94bnguGLJI/0jzS6r+ln8dCg79L12TCh8IMVeyb0q0cy0wVlQEownydJBN8L DUaKFVM9pGJZnTYi5IsqNZr7llPojR/A7NcOBpn23iXHBP5vq5p2N7OAaSc2tQ479vmW FXoWt6XR6KjnQTTCnmkT83XB7Ge6J6VIcZhKvdtO+i6uN+mDL5eAFAfgKVY61mVpn0F8 49t3vemey0dJH2oGmg0n4Miu8BV0EnFNZGObujsF8mIKlgv8frXloYbGvt3teaGQHVw5 LOkg== X-Gm-Message-State: APjAAAUXKMOiFLWsBF1P8dPr0jABSItMXYJL78lmQjnzTyJ+Nq6uxywl oonlng+toXO7SITBeW3+r9MWUQJN1rJi+FHuqLTGjA== X-Google-Smtp-Source: APXvYqyfBXA9XmXbGZHqcWD0t0USlZpN+WDbCnrmpXLdBk+4LqbchAml/Mo4CSWEgwoiXHjQ8mHI9xNYcHbD44LAJNo= X-Received: by 2002:a19:c7ca:: with SMTP id x193mr3592234lff.151.1562908429171; Thu, 11 Jul 2019 22:13:49 -0700 (PDT) MIME-Version: 1.0 References: <1562337154-26376-1-git-send-email-sumit.garg@linaro.org> <20190711192215.5w3fzdjwsebgoesh@linux.intel.com> In-Reply-To: <20190711192215.5w3fzdjwsebgoesh@linux.intel.com> From: Sumit Garg Date: Fri, 12 Jul 2019 10:43:38 +0530 Message-ID: Subject: Re: [RFC/RFT] KEYS: trusted: Add generic trusted keys framework To: Jarkko Sakkinen Cc: keyrings@vger.kernel.org, linux-integrity@vger.kernel.org, "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , linux-security-module@vger.kernel.org, dhowells@redhat.com, Herbert Xu , davem@davemloft.net, jejb@linux.ibm.com, Mimi Zohar , jmorris@namei.org, serge@hallyn.com, Casey Schaufler , Ard Biesheuvel , Daniel Thompson , Linux Kernel Mailing List , tee-dev@lists.linaro.org Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk List-ID: On Fri, 12 Jul 2019 at 00:52, Jarkko Sakkinen wrote: > > On Fri, Jul 05, 2019 at 08:02:34PM +0530, Sumit Garg wrote: > > Current trusted keys framework is tightly coupled to use TPM device as > > an underlying implementation which makes it difficult for implementations > > like Trusted Execution Environment (TEE) etc. to provide trusked keys > > support in case platform doesn't posses a TPM device. > > > > So this patch tries to add generic trusted keys framework where underlying > > implemtations like TPM, TEE etc. could be easily plugged-in. > > > > Suggested-by: Jarkko Sakkinen > > 1. Needs to be somehow dissected into digestable/reviewable pieces. Sure, will try to split this patch in next version. > 2. As a precursory step probably would make sense to move all > existing trusted keys code into one subsystem first. Okay. -Sumit > > /Jarkko