From: "Peter Huewe" <PeterHuewe@gmx.de>
To: tpmdd-devel@lists.sourceforge.net
Cc: keyrings@linux-nfs.org, jarkko.sakkinnen@linux.intel.com,
ksummit-discuss@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, james.l.morris@oracle.com,
linux-ima-devel@lists.sourceforge.net,
trousers-tech@lists.sourceforge.net
Subject: [Ksummit-discuss] TPM MiniSummit @ LinuxCon Europe
Date: Mon, 22 Sep 2014 11:01:31 +0200 [thread overview]
Message-ID: <trinity-2d36367c-59c5-44af-8737-fb503e10af38-1411376491498@3capp-gmx-bs07> (raw)
Hi,
I would like to 'invite' all interested parties in a short TPM minisummit where we can discuss the following hot topics of the TPM subsystem over a beer or two:
- State of the TPM Subsystem
- De-/Initialization Mess
- Devm'ification
- Testing
- TPM 2.0 Support
- Dependencies / interaction with other subsystems (e.g. keyring / IMA)
- Status of old 1.1b TPM drivers, deprecation plans
- ...
Please register your interest by filling out this doodle
http://doodle.com/q9ezcrivhqrktw6u
I'm not sure if I can get any funding for the summit... but maybe I can arrange something.
Also I'm trying to bring along some TPM samples from my employer if possible.
Thanks
Peter
p.s.: experienced kernel developers welcome :)
next reply other threads:[~2014-09-22 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 9:01 Peter Huewe [this message]
2014-09-23 16:42 ` Andy Lutomirski
2014-10-07 17:54 ` [Ksummit-discuss] [TrouSerS-tech] " Stefan Berger
2014-10-07 17:58 ` Andy Lutomirski
2014-10-07 18:02 ` [Ksummit-discuss] [tpmdd-devel] " Jason Gunthorpe
2014-10-07 18:47 ` Stefan Berger
2014-10-07 18:59 ` Andy Lutomirski
2014-10-13 0:03 ` Mimi Zohar
2014-10-08 20:59 ` Josh Triplett
2014-10-07 19:22 ` [Ksummit-discuss] " Jarkko Sakkinen
2014-10-12 23:45 ` [Ksummit-discuss] [tpmdd-devel] " Mimi Zohar
2014-10-12 18:17 ` [Ksummit-discuss] [tpmdd-devel] " Jarkko Sakkinen
2014-10-12 21:16 ` Peter Huewe
2014-10-13 5:17 ` Peter Huewe
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=trinity-2d36367c-59c5-44af-8737-fb503e10af38-1411376491498@3capp-gmx-bs07 \
--to=peterhuewe@gmx.de \
--cc=james.l.morris@oracle.com \
--cc=jarkko.sakkinnen@linux.intel.com \
--cc=keyrings@linux-nfs.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=trousers-tech@lists.sourceforge.net \
/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