From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: peterhuewe@gmx.de, tpmdd-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, safford@us.ibm.com
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
"Berg, Christopher" <Christopher.Berg@atmel.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
keyrings@linux-nfs.org (open list:KEYS-TRUSTED),
linux-security-module@vger.kernel.org (open list:KEYS-TRUSTED)
Subject: [PATCH 0/4] Basic trusted keys support for TPM 2.0
Date: Fri, 3 Jul 2015 18:36:32 +0300 [thread overview]
Message-ID: <1435937799-28040-1-git-send-email-jarkko.sakkinen@linux.intel.com> (raw)
Jarkko Sakkinen (4):
tpm: introduce struct tpm_buf
trusted: move struct trusted_key_options to trusted-type.h
tpm: seal/unseal for TPM 2.0
keys, trusted: seal/unseal with TPM 2.0 chips
drivers/char/tpm/tpm-interface.c | 75 ++++++
drivers/char/tpm/tpm.h | 77 ++++++
drivers/char/tpm/tpm2-cmd.c | 489 +++++++++++++++++++++++----------------
include/keys/trusted-type.h | 13 ++
include/linux/tpm.h | 26 +++
include/linux/tpm_command.h | 1 -
security/keys/trusted.c | 18 +-
security/keys/trusted.h | 18 +-
8 files changed, 496 insertions(+), 221 deletions(-)
--
2.1.4
next reply other threads:[~2015-07-03 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 15:36 Jarkko Sakkinen [this message]
2015-07-03 15:36 ` [PATCH 1/4] tpm: introduce struct tpm_buf Jarkko Sakkinen
2015-07-03 15:36 ` [PATCH 2/4] trusted: move struct trusted_key_options to trusted-type.h Jarkko Sakkinen
2015-07-03 15:36 ` [PATCH 3/4] tpm: seal/unseal for TPM 2.0 Jarkko Sakkinen
2015-07-03 15:36 ` [PATCH 4/4] keys, trusted: seal/unseal with TPM 2.0 chips Jarkko Sakkinen
2015-10-02 8:38 [PATCH 0/4] Basic trusted keys support for TPM 2.0 Jarkko Sakkinen
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=1435937799-28040-1-git-send-email-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=Christopher.Berg@atmel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=safford@us.ibm.com \
--cc=tpmdd-devel@lists.sourceforge.net \
/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
Powered by JetHome