From: Ken Goldman <kgoldman-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: RFC: "Hardened" trusted keys
Date: Tue, 13 Sep 2016 09:31:29 -0400 [thread overview]
Message-ID: <nr8v3d$md8$1@blaine.gmane.org> (raw)
In-Reply-To: <20160829190547.GA18827-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On 8/29/2016 3:05 PM, Jarkko Sakkinen wrote:
> After LSS2016 I got this idea of having hardened trusted keys for TPM2
> where the key material is never exposed to kernel. Child keys of a
> hardened trusted key would be unsealed using TPM2_EncryptDecrypt
> operation.
Beware that the TPM2_EncryptDecrypt command is optional. I know of at
least one TPM vendor that does not implement the command due to export
restrictions.
Why not seal to a parent symmetric key and use TPM2_Unseal? Unseal is
just a restricted decryption operation.
------------------------------------------------------------------------------
prev parent reply other threads:[~2016-09-13 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 19:05 RFC: "Hardened" trusted keys Jarkko Sakkinen
[not found] ` <20160829190547.GA18827-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-09-13 13:31 ` Ken Goldman [this message]
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='nr8v3d$md8$1@blaine.gmane.org' \
--to=kgoldman-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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).