Message ID | alpine.LRH.2.21.1810262033270.5228@namei.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT,PULL] security: keys updates for v4.20 | expand |
On Fri, Oct 26, 2018 at 2:36 AM James Morris <jmorris@namei.org> wrote: > > From David: "Provide five new operations in the key_type struct that can > be used to provide access to asymmetric key operations. These will be > implemented for the asymmetric key type in a later patch and may refer to > a key retained in RAM by the kernel or a key retained in crypto hardware. Pulled. However. I really would have expected some of the TPM people to have acked these, or at least looked at them. There was no sign of that in any of the tpm commits that I could see.. Hmm? Linus
On Thu, 1 Nov 2018, Linus Torvalds wrote: > On Fri, Oct 26, 2018 at 2:36 AM James Morris <jmorris@namei.org> wrote: > > > > From David: "Provide five new operations in the key_type struct that can > > be used to provide access to asymmetric key operations. These will be > > implemented for the asymmetric key type in a later patch and may refer to > > a key retained in RAM by the kernel or a key retained in crypto hardware. > > Pulled. > > However. I really would have expected some of the TPM people to have > acked these, or at least looked at them. There was no sign of that in > any of the tpm commits that I could see.. > > Hmm? Good poin. I'll ensure the linux-integrity list (now cc'd) is always included when asking for review of code which touches TPM.