[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190804204807.ajhy3jhwie3oq6d5@linux.intel.com>
Date: Sun, 4 Aug 2019 23:48:07 +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,
casey@...aufler-ca.com, ard.biesheuvel@...aro.org,
daniel.thompson@...aro.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
tee-dev@...ts.linaro.org
Subject: Re: [RFC v2 0/6] Introduce TEE based Trusted Keys support
On Tue, Jul 30, 2019 at 05:53:34PM +0530, Sumit Garg wrote:
> tee: optee: allow kernel pages to register as shm
> tee: enable support to register kernel memory
> tee: add private login method for kernel clients
> KEYS: trusted: Introduce TEE based Trusted Keys
> doc: keys: Document usage of TEE based Trusted Keys
> MAINTAINERS: Add entry for TEE based Trusted Keys
Skimmed through the patches. I think it is better to sort out the
current LKM dependency issue with trusted.ko and get TPM 1.2 and TPM 2.0
trusted keys code consolidated before it makes sense to really go detail
on this.
/Jarkko
Powered by blists - more mailing lists