[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9f346e6d-04f2-b8cd-bf67-f1cee59d9630@linux.microsoft.com>
Date: Fri, 20 Dec 2019 12:50:34 -0800
From: Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>
To: Mimi Zohar <zohar@...ux.ibm.com>,
James.Bottomley@...senPartnership.com,
linux-integrity@...r.kernel.org
Cc: eric.snowberg@...cle.com, dhowells@...hat.com,
mathew.j.martineau@...ux.intel.com, matthewgarrett@...gle.com,
sashal@...nel.org, jamorris@...ux.microsoft.com,
linux-kernel@...r.kernel.org, keyrings@...r.kernel.org
Subject: Re: [PATCH v5 0/2] IMA: Deferred measurement of keys
On 12/20/19 11:36 AM, Mimi Zohar wrote:
>>
>> Shall I create a new patch set to address that and have that be reviewed
>> independent of this patch set?
>
> If it is just a single additional patch, feel free to post it without
> a cover letter.
Sure
>>
>> Like you'd suggested earlier, we can wait for a certain time, after IMA
>> is initialized, and free the queue if a custom policy was not loaded.
>
> Different types of systems vary in boot time, but perhaps a certain
> amount of time after IMA is initialized would be consistent. This
> would need to work for IoT devices/sensors to servers.
>
> Mimi
>
Yes - I agree.
thanks,
-lakshmi
Powered by blists - more mailing lists