From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.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] [tpmdd-devel] [TrouSerS-tech] TPM MiniSummit @ LinuxCon Europe
Date: Tue, 07 Oct 2014 14:47:06 -0400 [thread overview]
Message-ID: <5434352A.6080403@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141007180209.GD10432@obsidianresearch.com>
On 10/07/2014 02:02 PM, Jason Gunthorpe wrote:
> On Tue, Oct 07, 2014 at 01:54:41PM -0400, Stefan Berger wrote:
>
>> 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.
> How does trousers work with the kernel when the kernel is also using
> TPM key slots for IMA/keyring/whatever?
IIRC it only uses a single key slot and swaps all keys in and out of
that one. If the kernel was to fill up all key (and sessions) slots, TSS
would probably not work anymore.
Another argument for the TSS is that you also wouldn't want applications
to swap out each others keys and sessions and leave them out or assume
that they would always cleanup if they do not currently need them.
Regards,
Stefan
next prev parent reply other threads:[~2014-10-07 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 9:01 [Ksummit-discuss] " Peter Huewe
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 [this message]
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=5434352A.6080403@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=james.l.morris@oracle.com \
--cc=jarkko.sakkinnen@linux.intel.com \
--cc=jgunthorpe@obsidianresearch.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