ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Peter Huewe <PeterHuewe@gmx.de>
Cc: keyrings@linux-nfs.org, jarkko.sakkinnen@linux.intel.com,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	LSM List <linux-security-module@vger.kernel.org>,
	tpmdd-devel@lists.sourceforge.net,
	James Morris <james.l.morris@oracle.com>,
	linux-ima-devel@lists.sourceforge.net,
	trousers-tech@lists.sourceforge.net
Subject: Re: [Ksummit-discuss] TPM MiniSummit @ LinuxCon Europe
Date: Tue, 23 Sep 2014 09:42:33 -0700	[thread overview]
Message-ID: <CALCETrWdPmSCUkb-neH5ssNmxzsqY0rioQq5qMc2ne7J0JxVLg@mail.gmail.com> (raw)
In-Reply-To: <trinity-2d36367c-59c5-44af-8737-fb503e10af38-1411376491498@3capp-gmx-bs07>

On Sep 22, 2014 2:07 AM, "Peter Huewe" <PeterHuewe@gmx.de> wrote:
>
> 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
>  - ...
>

I am unlikely to be there, but I have a feature request / food for thought:

Using a mandatory userspace daemon (e.g. trousers) for TPM access
sucks.  Might it be possible to teach the kernel to handle context
save and restore and let multiple processes open the device at once?
Then a daemon wouldn't be necessary.

There would still be a need for some policy (e.g. who can clear the
SRK), but that should be manageable.  Maybe there should be two device
nodes.  /dev/tpm_unpriv would be fully virtualized for access by
multiple processes, but it would only allow use of the key hierarchy
and read access to PCRs.  /dev/tpm_priv would allow NV access, PCR
writes, SRK clears, etc.

--Andy

>
> 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 :)
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

  reply	other threads:[~2014-09-23 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22  9:01 Peter Huewe
2014-09-23 16:42 ` Andy Lutomirski [this message]
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=CALCETrWdPmSCUkb-neH5ssNmxzsqY0rioQq5qMc2ne7J0JxVLg@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=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