All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
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] [TrouSerS-tech] TPM MiniSummit @ LinuxCon Europe
Date: Tue, 7 Oct 2014 22:22:10 +0300	[thread overview]
Message-ID: <20141007192210.GB31645@intel.com> (raw)
In-Reply-To: <543428E1.7050702@linux.vnet.ibm.com>

On Tue, Oct 07, 2014 at 01:54:41PM -0400, Stefan Berger wrote:
> On 09/23/2014 12:42 PM, Andy Lutomirski wrote:
> >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.
> 
> Why add the complexity of swapping of authenticated sessions and keys into
> the kernel if you can handle this in userspace? You need a library that is
> aware of the number of key slots and slots for sessions in the TPM and swaps
> them in at out when applications need them. Trousers is such a library that
> was designed to cope with the limitations of the device and make its
> functionality available to all applications that want to access it.

One justification might be that kernel is also using TPM? TrouSerS can
not manage session for kernel internal use.

>    Stefan

/Jarkko

WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Peter Huewe <PeterHuewe@gmx.de>,
	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: [TrouSerS-tech] [Ksummit-discuss] TPM MiniSummit @ LinuxCon Europe
Date: Tue, 7 Oct 2014 22:22:10 +0300	[thread overview]
Message-ID: <20141007192210.GB31645@intel.com> (raw)
In-Reply-To: <543428E1.7050702@linux.vnet.ibm.com>

On Tue, Oct 07, 2014 at 01:54:41PM -0400, Stefan Berger wrote:
> On 09/23/2014 12:42 PM, Andy Lutomirski wrote:
> >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.
> 
> Why add the complexity of swapping of authenticated sessions and keys into
> the kernel if you can handle this in userspace? You need a library that is
> aware of the number of key slots and slots for sessions in the TPM and swaps
> them in at out when applications need them. Trousers is such a library that
> was designed to cope with the limitations of the device and make its
> functionality available to all applications that want to access it.

One justification might be that kernel is also using TPM? TrouSerS can
not manage session for kernel internal use.

>    Stefan

/Jarkko

  parent reply	other threads:[~2014-10-07 19:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22  9:01 [Ksummit-discuss] TPM MiniSummit @ LinuxCon Europe Peter Huewe
2014-09-22  9:01 ` Peter Huewe
2014-09-23 16:42 ` [Ksummit-discuss] " Andy Lutomirski
2014-09-23 16:42   ` Andy Lutomirski
2014-10-07 17:54   ` [Ksummit-discuss] [TrouSerS-tech] " Stefan Berger
2014-10-07 17:54     ` [TrouSerS-tech] [Ksummit-discuss] " Stefan Berger
2014-10-07 17:58     ` [Ksummit-discuss] [TrouSerS-tech] " Andy Lutomirski
2014-10-07 17:58       ` [TrouSerS-tech] [Ksummit-discuss] " Andy Lutomirski
2014-10-07 18:02     ` [Ksummit-discuss] [tpmdd-devel] [TrouSerS-tech] " Jason Gunthorpe
2014-10-07 18:02       ` [tpmdd-devel] [TrouSerS-tech] [Ksummit-discuss] " Jason Gunthorpe
2014-10-07 18:47       ` [Ksummit-discuss] [tpmdd-devel] [TrouSerS-tech] " Stefan Berger
2014-10-07 18:47         ` [tpmdd-devel] [TrouSerS-tech] [Ksummit-discuss] " Stefan Berger
2014-10-07 18:59         ` [Ksummit-discuss] [tpmdd-devel] [TrouSerS-tech] " Andy Lutomirski
2014-10-07 18:59           ` [tpmdd-devel] [TrouSerS-tech] [Ksummit-discuss] " Andy Lutomirski
2014-10-13  0:03           ` [Ksummit-discuss] [tpmdd-devel] [TrouSerS-tech] " Mimi Zohar
2014-10-13  0:03             ` [tpmdd-devel] [TrouSerS-tech] [Ksummit-discuss] " Mimi Zohar
2014-10-08 20:59         ` [Ksummit-discuss] [tpmdd-devel] [TrouSerS-tech] " Josh Triplett
2014-10-08 20:59           ` Josh Triplett
2014-10-07 19:22     ` Jarkko Sakkinen [this message]
2014-10-07 19:22       ` [TrouSerS-tech] [Ksummit-discuss] " Jarkko Sakkinen
2014-10-12 23:45       ` [Ksummit-discuss] [tpmdd-devel] [TrouSerS-tech] " Mimi Zohar
2014-10-12 23:45         ` [tpmdd-devel] [TrouSerS-tech] [Ksummit-discuss] " Mimi Zohar
2014-10-12 18:17   ` [Ksummit-discuss] [tpmdd-devel] " Jarkko Sakkinen
2014-10-12 18:17     ` [tpmdd-devel] [Ksummit-discuss] " Jarkko Sakkinen
2014-10-12 21:16     ` [Ksummit-discuss] [tpmdd-devel] " Peter Huewe
2014-10-12 21:16       ` Aw: Re: [tpmdd-devel] [Ksummit-discuss] " Peter Huewe
2014-10-13  5:17       ` [Ksummit-discuss] [tpmdd-devel] " Peter Huewe
2014-10-13  5:17         ` Aw: Re: [tpmdd-devel] [Ksummit-discuss] " 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=20141007192210.GB31645@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --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=stefanb@linux.vnet.ibm.com \
    --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 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.