linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>,
	linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>,
	David Woodhouse <dwmw2@infradead.org>,
	keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v10 2/8] oid_registry: Add TCG defined OIDS for TPM keys
Date: Tue, 23 Jun 2020 01:04:44 +0300	[thread overview]
Message-ID: <20200622220444.GG22727@linux.intel.com> (raw)
In-Reply-To: <1592508122.15159.7.camel@HansenPartnership.com>

On Thu, Jun 18, 2020 at 12:22:02PM -0700, James Bottomley wrote:
> On Thu, 2020-06-18 at 10:14 +0300, Jarkko Sakkinen wrote:
> > On Wed, Jun 17, 2020 at 05:25:40PM -0700, James Bottomley wrote:
> > > On Wed, 2020-06-17 at 14:42 -0700, Jerry Snitselaar wrote:
> > > > On Tue Jun 16 20, James Bottomley wrote:
> > > > > The TCG has defined an OID prefix "2.23.133.10.1" for the
> > > > > various
> > > > > TPM
> > > > > key uses.  We've defined three of the available numbers:
> > > > > 
> > > > > 2.23.133.10.1.3 TPM Loadable key.  This is an asymmetric key
> > > > > (Usually
> > > > > 		RSA2048 or Elliptic Curve) which can be
> > > > > imported by a
> > > > > 		TPM2_Load() operation.
> > > > > 
> > > > > 2.23.133.10.1.4 TPM Importable Key.  This is an asymmetric key
> > > > > (Usually
> > > > > 		RSA2048 or Elliptic Curve) which can be
> > > > > imported by a
> > > > > 		TPM2_Import() operation.
> > > > > 
> > > > > Both loadable and importable keys are specific to a given TPM,
> > > > > the
> > > > > difference is that a loadable key is wrapped with the symmetric
> > > > > secret, so must have been created by the TPM itself.  An
> > > > > importable
> > > > > key is wrapped with a DH shared secret, and may be created
> > > > > without
> > > > > access to the TPM provided you know the public part of the
> > > > > parent
> > > > > key.
> > > > > 
> > > > > 2.23.133.10.1.5 TPM Sealed Data.  This is a set of data (up to
> > > > > 128
> > > > > 		bytes) which is sealed by the TPM.  It usually
> > > > > 		represents a symmetric key and must be unsealed
> > > > > before
> > > > > 		use.
> > > > > 
> > > > 
> > > > James, which document are these defined in? I was searching last
> > > > night, and couldn't find it.
> > > 
> > > It isn't.  It's defined in a TCG spreadsheet that Monty Wiseman
> > > keeps, but that seems to be as "official" as it gets with the TCG
> > > OID registry.
> > > 
> > > James
> > 
> > "The TCG has defined an OID prefix "2.23.133.10.1" for the various
> > TPM key uses."
> > 
> > Should this sentence start just as "TCG ...", not sure if "the" is
> > required?
> 
> I've always referred to it as The Trusted Computing Group (so the TCG)
> partly to show they're not just any old trusted computing group.  But I
> think they mostly do refer to themselves in literature as TCG.

... not that this highly important, just asking for pure interest :-)

/Jarkko

  reply	other threads:[~2020-06-22 22:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 16:02 [PATCH v10 0/8] TPM 2.0 trusted keys with attached policy James Bottomley
2020-06-16 16:02 ` [PATCH v10 1/8] lib: add ASN.1 encoder James Bottomley
2020-06-16 16:02 ` [PATCH v10 2/8] oid_registry: Add TCG defined OIDS for TPM keys James Bottomley
2020-06-17 21:42   ` Jerry Snitselaar
2020-06-18  0:25     ` James Bottomley
2020-06-18  7:14       ` Jarkko Sakkinen
2020-06-18 19:22         ` James Bottomley
2020-06-22 22:04           ` Jarkko Sakkinen [this message]
2020-06-16 16:02 ` [PATCH v10 3/8] security: keys: trusted: fix TPM2 authorizations James Bottomley
2020-06-16 16:02 ` [PATCH v10 4/8] security: keys: trusted: use ASN.1 TPM2 key format for the blobs James Bottomley
2020-06-16 16:02 ` [PATCH v10 5/8] security: keys: trusted: Make sealed key properly interoperable James Bottomley
2020-06-17 23:46   ` Jarkko Sakkinen
2020-06-16 16:02 ` [PATCH v10 6/8] security: keys: trusted: add PCR policy to TPM2 keys James Bottomley
2020-06-17 23:44   ` Jarkko Sakkinen
2020-06-16 16:02 ` [PATCH v10 7/8] security: keys: trusted: add ability to specify arbitrary policy James Bottomley
2020-06-17 23:42   ` Jarkko Sakkinen
2020-06-18  0:27     ` James Bottomley
2020-06-18  7:12       ` Jarkko Sakkinen
2020-06-18 19:45         ` James Bottomley
2020-06-23  0:46           ` Jarkko Sakkinen
2020-06-16 16:02 ` [PATCH v10 8/8] security: keys: trusted: implement counter/timer policy James Bottomley

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=20200622220444.GG22727@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jsnitsel@redhat.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.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).