[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190613153202.GF18488@linux.intel.com>
Date: Thu, 13 Jun 2019 18:32:02 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Sumit Garg <sumit.garg@...aro.org>
Cc: keyrings@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, jens.wiklander@...aro.org,
corbet@....net, dhowells@...hat.com, jejb@...ux.ibm.com,
zohar@...ux.ibm.com, jmorris@...ei.org, serge@...lyn.com,
ard.biesheuvel@...aro.org, daniel.thompson@...aro.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
tee-dev@...ts.linaro.org
Subject: Re: [RFC 4/7] KEYS: trusted: Introduce TEE based Trusted Keys
On Thu, Jun 13, 2019 at 04:00:30PM +0530, Sumit Garg wrote:
> Add support for TEE based trusted keys where TEE provides the functionality
> to seal and unseal trusted keys using hardware unique key.
>
> Refer to Documentation/tee.txt for detailed information about TEE.
>
> Approach taken in this patch acts as an alternative to a TPM device in case
> platform doesn't possess one.
>
> Signed-off-by: Sumit Garg <sumit.garg@...aro.org>
How does this interact with the trusted module? Why there is no update
to security/keys/trusted-encrypted.txt?
Somehow the existing trusted module needs to be re-architected to work
with either. Otherwise, this will turn out to be a mess.
/Jarkko
Powered by blists - more mailing lists