From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id B2FEC99A for ; Sun, 12 Oct 2014 18:17:27 +0000 (UTC) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 368EA2026B for ; Sun, 12 Oct 2014 18:17:27 +0000 (UTC) Date: Sun, 12 Oct 2014 21:17:21 +0300 From: Jarkko Sakkinen To: Andy Lutomirski Message-ID: <20141012181721.GB5495@intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: keyrings@linux-nfs.org, jarkko.sakkinnen@linux.intel.com, "ksummit-discuss@lists.linuxfoundation.org" , "linux-kernel@vger.kernel.org" , LSM List , tpmdd-devel@lists.sourceforge.net, James Morris , linux-ima-devel@lists.sourceforge.net, trousers-tech@lists.sourceforge.net Subject: Re: [Ksummit-discuss] [tpmdd-devel] TPM MiniSummit @ LinuxCon Europe List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hey, apologies for top-posting but which day/time/place is this going to be held? /Jarkko On Tue, Sep 23, 2014 at 09:42:33AM -0700, Andy Lutomirski wrote: > On Sep 22, 2014 2:07 AM, "Peter Huewe" 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 > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > tpmdd-devel mailing list > tpmdd-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tpmdd-devel