From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Peter Huewe <peterhuewe@gmx.de>,
Marcel Selhorst <tpmdd@selhorst.net>,
David Howells <dhowells@redhat.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
James Morris <james.l.morris@oracle.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
"open list:KEYS-ENCRYPTED" <keyrings@vger.kernel.org>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
"open list:CRYPTO API" <linux-crypto@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:KEYS-ENCRYPTED"
<linux-security-module@vger.kernel.org>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>
Subject: [PATCH 0/2] TPM 2.0 trusted key features for v4.5
Date: Tue, 17 Nov 2015 18:27:20 +0200 [thread overview]
Message-ID: <1447777643-10777-1-git-send-email-jarkko.sakkinen@linux.intel.com> (raw)
These are the remaining features to enable trusted keys for TPM 2.0 that very
not finished by the v4.4 merge window. These patches enable authorization
policy based sealing (like using PCRs together with a password for example or
something more complicated) with a user selected hash algorithm.
Jarkko Sakkinen (2):
keys, trusted: select hash algorithm for TPM2 chips
keys, trusted: seal with a policy
Documentation/security/keys-trusted-encrypted.txt | 31 ++++++----
crypto/hash_info.c | 2 +
drivers/char/tpm/tpm.h | 10 +++-
drivers/char/tpm/tpm2-cmd.c | 60 ++++++++++++++++---
include/crypto/hash_info.h | 3 +
include/keys/trusted-type.h | 4 ++
include/uapi/linux/hash_info.h | 1 +
security/keys/Kconfig | 1 +
security/keys/trusted.c | 73 ++++++++++++++++++++++-
9 files changed, 161 insertions(+), 24 deletions(-)
--
2.5.0
next reply other threads:[~2015-11-17 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 16:27 Jarkko Sakkinen [this message]
2015-11-17 16:27 ` [PATCH 1/2] keys, trusted: select hash algorithm for TPM2 chips 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=1447777643-10777-1-git-send-email-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.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;
as well as URLs for NNTP newsgroup(s).