[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <aa84ca0a-f976-bf22-9cfd-40405c8f3ef8@linux.vnet.ibm.com>
Date: Tue, 16 May 2017 15:32:33 -0400
From: Stefan Berger <stefanb@...ux.vnet.ibm.com>
To: Ken Goldman <kgold@...ux.vnet.ibm.com>,
tpmdd-devel@...ts.sourceforge.net,
linux-security-module@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [tpmdd-devel] [PATCH v4 2/2] tpm: vtpm_proxy: Implement
request_locality function.
On 05/16/2017 03:03 PM, Ken Goldman wrote:
> On 5/10/2017 7:54 PM, Stefan Berger wrote:
>> Implement the request_locality function. To set the locality on the
>> backend we define vendor-specific TPM 1.2 and TPM 2 ordinals and send
>> a command to the backend to set the locality for the next commands.
>
> When this says "for the next commands", does that mean that the locality
> is fixed for all commands until a new request_locality is sent to
> change it?
Yes.
Powered by blists - more mailing lists