[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170130214643.tvwjzc2whpczxqdt@intel.com>
Date: Mon, 30 Jan 2017 23:46:43 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Ken Goldman <kgoldman@...ibm.com>
Cc: tpmdd-devel@...ts.sourceforge.net,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [tpmdd-devel] [PATCH v2 1/2] tpm2: add session handle context
saving and restoring to the space code
On Sun, Jan 29, 2017 at 07:35:32PM -0500, Ken Goldman wrote:
> On 1/27/2017 7:32 PM, James Bottomley wrote:
> >
> > Sessions are also isolated during each instance of a tpm space. This
> > means that spaces shouldn't be able to see each other's sessions and
> > is enforced by ensuring that a space user may only refer to sessions
> > handles that are present in their own chip->session_tbl. Finally when
> > a space is closed, all the sessions belonging to it should be flushed
> > so the handles may be re-used by other spaces.
>
> This should be true for transient objects as well.
Transient objects do not need anything special. All transient objects
are flushed after command-response so you implicitly get the isolation.
/Jarkko
Powered by blists - more mailing lists