From: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RFC: "Hardened" trusted keys
Date: Mon, 29 Aug 2016 22:05:47 +0300 [thread overview]
Message-ID: <20160829190547.GA18827@intel.com> (raw)
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.
To retain backwards compatibility with the exiting trusted keys format,
this would probably require a new option to keyctl.
This is not my priority at the moment but just wanted to mirror does
this sound like a grazy idea?
/Jarkko
------------------------------------------------------------------------------
next reply other threads:[~2016-08-29 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 19:05 Jarkko Sakkinen [this message]
[not found] ` <20160829190547.GA18827-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-09-13 13:31 ` RFC: "Hardened" trusted keys Ken Goldman
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=20160829190547.GA18827@intel.com \
--to=jarkko.sakkinen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=keyrings-u79uwXL29TY76Z2rM5mHXA@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).