[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5411bc3d-74eb-6868-5768-bba3726a661a@linux.microsoft.com>
Date: Thu, 9 Jan 2020 08:38:11 -0800
From: Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>
To: Mimi Zohar <zohar@...ux.ibm.com>,
James.Bottomley@...senPartnership.com, arnd@...db.de,
linux-integrity@...r.kernel.org
Cc: dhowells@...hat.com, sashal@...nel.org,
linux-kernel@...r.kernel.org, keyrings@...r.kernel.org,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH v1] IMA: fix measuring asymmetric keys Kconfig
On 1/8/20 8:52 PM, Mimi Zohar wrote:
>
> For the time being, I've pushed out this patch with the existing patch
> description to next-integrity-testing, but the patch description
> should be rewritten clearer. For example,
>
> As a result of the asymmetric public keys subtype being defined as a
> tristate, with the existing IMA Makefile, ima_asymmetric_keys.c could
> be built as a kernel module. To prevent this from happening, this
> patch defines and uses an intermediate Kconfig boolean option named
> IMA_MEASURE_ASYMMETRIC_KEYS.
>
> Please let me know if you're ok with this wording.
>
> thanks,
>
> Mimi
>
That sounds perfect. Thanks for your help Mimi.
-lakshmi
Powered by blists - more mailing lists