From: Sumit Garg <sumit.garg@linaro.org>
To: keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org
Cc: dhowells@redhat.com, herbert@gondor.apana.org.au,
davem@davemloft.net, peterhuewe@gmx.de, jgg@ziepe.ca,
jejb@linux.ibm.com, jarkko.sakkinen@linux.intel.com,
arnd@arndb.de, gregkh@linuxfoundation.org, zohar@linux.ibm.com,
jmorris@namei.org, serge@hallyn.com, casey@schaufler-ca.com,
ard.biesheuvel@linaro.org, daniel.thompson@linaro.org,
linux-kernel@vger.kernel.org, tee-dev@lists.linaro.org,
Sumit Garg <sumit.garg@linaro.org>
Subject: [RFC/RFT v3 0/3] KEYS: trusted: Add generic trusted keys framework
Date: Tue, 6 Aug 2019 19:07:17 +0530 [thread overview]
Message-ID: <1565098640-12536-1-git-send-email-sumit.garg@linaro.org> (raw)
This patch-set is an outcome of discussion here [1].
I have tested this framework with trusted keys support provided via TEE
but I wasn't able to test it with a TPM device as I don't possess one. It
would be really helpful if others could test this patch-set using a TPM
device.
[1] https://www.mail-archive.com/linux-doc@vger.kernel.org/msg30591.html
Changes in v3:
Move TPM2 trusted keys code to trusted keys subsystem.
Changes in v2:
Split trusted keys abstraction patch for ease of review.
Sumit Garg (3):
KEYS: trusted: create trusted keys subsystem
KEYS: trusted: move tpm2 trusted keys code
KEYS: trusted: Add generic trusted keys framework
crypto/asymmetric_keys/asym_tpm.c | 2 +-
drivers/char/tpm/tpm-interface.c | 56 ---
drivers/char/tpm/tpm.h | 224 ------------
drivers/char/tpm/tpm2-cmd.c | 307 -----------------
include/keys/trusted-type.h | 45 +++
include/keys/{trusted.h => trusted_tpm.h} | 42 +--
include/linux/tpm.h | 264 +++++++++++++-
security/keys/Makefile | 2 +-
security/keys/trusted-keys/Makefile | 8 +
.../keys/{trusted.c => trusted-keys/trusted-tpm.c} | 363 ++++----------------
security/keys/trusted-keys/trusted-tpm2.c | 378 +++++++++++++++++++++
security/keys/trusted-keys/trusted.c | 343 +++++++++++++++++++
12 files changed, 1109 insertions(+), 925 deletions(-)
rename include/keys/{trusted.h => trusted_tpm.h} (72%)
create mode 100644 security/keys/trusted-keys/Makefile
rename security/keys/{trusted.c => trusted-keys/trusted-tpm.c} (76%)
create mode 100644 security/keys/trusted-keys/trusted-tpm2.c
create mode 100644 security/keys/trusted-keys/trusted.c
--
2.7.4
next reply other threads:[~2019-08-06 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 13:37 Sumit Garg [this message]
2019-08-06 13:37 ` [RFC/RFT v3 1/3] KEYS: trusted: create trusted keys subsystem Sumit Garg
2019-08-07 18:59 ` Jarkko Sakkinen
2019-08-08 12:26 ` Sumit Garg
2019-08-06 13:37 ` [RFC/RFT v3 2/3] KEYS: trusted: move tpm2 trusted keys code Sumit Garg
2019-08-06 13:43 ` Greg KH
2019-08-06 13:55 ` Sumit Garg
2019-08-07 19:03 ` Jarkko Sakkinen
2019-08-08 13:21 ` Sumit Garg
2019-08-08 15:15 ` Jarkko Sakkinen
2019-08-13 7:59 ` Sumit Garg
2019-08-06 13:37 ` [RFC/RFT v3 3/3] KEYS: trusted: Add generic trusted keys framework Sumit Garg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1565098640-12536-1-git-send-email-sumit.garg@linaro.org \
--to=sumit.garg@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=casey@schaufler-ca.com \
--cc=daniel.thompson@linaro.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=serge@hallyn.com \
--cc=tee-dev@lists.linaro.org \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).