[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <db5ea3c2-42df-420b-6813-f6ef2c30df6f@pengutronix.de>
Date: Mon, 11 Oct 2021 12:19:19 +0200
From: Ahmad Fatoum <a.fatoum@...gutronix.de>
To: Andreas Rammhold <andreas@...mhold.de>,
Mimi Zohar <zohar@...ux.ibm.com>,
David Howells <dhowells@...hat.com>,
Jarkko Sakkinen <jarkko@...nel.org>,
James Bottomley <jejb@...ux.ibm.com>
Cc: James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Sumit Garg <sumit.garg@...aro.org>,
linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] KEYS: trusted: Fix trusted key backends when building
as module
Hello Mimi, David, Jarkko and James,
On 02.10.21 23:47, Andreas Rammhold wrote:
>> My mistake. Trusted and encrypted key types have always been defined
>> as tristate. Only when EVM selects encrypted keys, and by extension
>> trusted keys, are they builtin.
>
> So how do we go about this patch? Building the TPM support as module has
> broken actually using the trusted backend. This patch fixes that while
> still allowing it to be a builtin. If there is some configuration there
> a module isn't acceptable I am sure that is handled within Kconfig?
Can anyone of you four pick this up? Andreas' regression fix has
had Jarkko's Reviewed-by for close to two months and a half now.
Thanks,
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists