All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner at gmail.com>
To: tpm2@lists.01.org
Subject: [tpm2] meta-measured updates
Date: Wed, 30 May 2018 17:13:04 -0400	[thread overview]
Message-ID: <20180530211304.GA11797@linux-uys3> (raw)

[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]

Hi Philip,

My hope is that one day the OE community will have one security layer to
choose, rather than the three that we have currently.

I've looked at the three different layers and feel that meta-secure-core might
be a better one to target. With respect to its TPM2 recipes, however,
meta-secure-core (and the other, meta-security) lag behind meta-measured. As
such I've been working on some updates for meta-secure-core.

Are you still keen to fold meta-measured into something else? If not I could
prepare a set of patches for meta-measured as well.

Looking at the master commit of tpm2-tss, specifically, I've noticed a number
of changes and was hoping for your feedback.

With the tss 1.x stuff we had:
	- libtcti-device
	- libtcti-socket
	- libsapi

The new tss 2.x stuff has:
	- libtss2-esys
	- libtss2-mu
	- libtss2-sys
	- libtss2-tcti-device
	- libtss2-tcti-mssim

I'm guessing libtss2-tcti-device is the new name for the old libtcti-device.
But are there any mappings from the new stuff to the older libtcti-socket and
libsapi?

It looks like things are going to get messy. It looks like, going forward,
we're going to need to keep tpm2-tss_1.x.bb around as well as create
tpm2-tss_2.x.bb recipes with differently named PACKAGES so existing recipes
that use tss (and expect the old 1.x behaviour/API) can continue to work while
allowing new code (or updates to the old) to use the new API (?).

Best regards,
	Trevor

             reply	other threads:[~2018-05-30 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 21:13 Trevor Woerner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-30 23:48 [tpm2] meta-measured updates Trevor Woerner
2018-05-31 21:14 Roberts, William C
2018-05-31 21:20 Trevor Woerner
2018-06-01 23:01 Philip Tricca
2018-06-02  2:35 Trevor Woerner

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=20180530211304.GA11797@linux-uys3 \
    --to=tpm2@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.