From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: TPM microconference at LPC
Date: Mon, 19 Sep 2016 18:50:11 +0100 [thread overview]
Message-ID: <20160919175011.GB22324@srcf.ucam.org> (raw)
Hi,
As previously mentioned, there'll be a TPM microconference at the Linux
Plumbers Conference in Santa Fe this November. The aim of these
microconferences is to discuss infrastructural and integration issues
around Linux, giving domain experts and distribution developers an
opportunity to figure out what problems exist and how best to solve
them.
We have a rough schedule which involves the following topics:
* An introduction to the TPM stack, the components that currently exist
and what we seem to be missing
* Discussion of the Intel and IBM TSS 2.0 stacks
* An overview of how Google make use of TPMs in ChromeOS and what their
stack looks like
* An attempt to figure out if there's any way we can ship known-good PCR
values for general-purpose distributions
* What needs to be done to make TPM-based credential (disk encryption,
ssh keys, and so on) storage practical
If anyone is interested and *hasn't* registered for LPC yet, I have a
small number of passes available. Please get in touch with me directly
in the next few days and we'll try to figure something out.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
------------------------------------------------------------------------------
next reply other threads:[~2016-09-19 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 17:50 Matthew Garrett [this message]
[not found] ` <20160919175011.GB22324-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2016-11-10 9:59 ` TPM microconference at LPC Peter.Huewe-d0qZbvYSIPpWk0Htik3J/w
[not found] ` <df4ace4655784b5588c66381a05f7960-FoTRpVxct+aJSz+rYg/bSJowlv4uC7bZ@public.gmane.org>
2016-11-10 10:24 ` Matthew Garrett
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=20160919175011.GB22324@srcf.ucam.org \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@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).