[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190805205915.k5enrfob2cocqyff@linux.intel.com>
Date: Mon, 5 Aug 2019 23:59:15 +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,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>,
linux-security-module@...r.kernel.org, dhowells@...hat.com,
Herbert Xu <herbert@...dor.apana.org.au>, davem@...emloft.net,
jejb@...ux.ibm.com, Mimi Zohar <zohar@...ux.ibm.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Casey Schaufler <casey@...aufler-ca.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Daniel Thompson <daniel.thompson@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"tee-dev @ lists . linaro . org" <tee-dev@...ts.linaro.org>
Subject: Re: [RFC/RFT v2 1/2] KEYS: trusted: create trusted keys subsystem
On Mon, Aug 05, 2019 at 10:32:59AM +0530, Sumit Garg wrote:
> Okay, I will try to move TPM2 trusted keys code also.
I'm definitely for extending trusted keys beyond TPMs. Before that can be
done, however, the current mess needs to be cleaned up.
I did a lot of work recently [1] to clean up TPM transmit code to better
suited to be used outside of the TPM drivers (remove recursive calls,
put the whole stack use tpm_buf for everything).
What still needs to be done is to move tpm_buf stuff to include/linux in
order to be usable in the keyring code. Also for TPM 2.0 trusted keys,
TPM2 constants need to be moved to include/linux. For the latter, I'd
suggest to move all protocol constants there and not just what is
required for trusted keys. Better to have them in one place.
[1] https://lkml.org/lkml/2019/2/13/176
/Jarkko
Powered by blists - more mailing lists