integrity: Load mokx variables into the blacklist keyring
authorEric Snowberg <eric.snowberg@oracle.com>
Fri, 22 Jan 2021 18:10:54 +0000 (13:10 -0500)
committerSasha Levin <sashal@kernel.org>
Wed, 30 Jun 2021 12:47:30 +0000 (08:47 -0400)
commit1573d595e2395c4d2742d2217d86f6241ca47b9f
tree5bca044d2d29f8aba0a8e3b292d7d1d97ca4595e
parentc6ae6f89fc4f7820d0ce6e8c1340d660b358e791
integrity: Load mokx variables into the blacklist keyring

[ Upstream commit ebd9c2ae369a45bdd9f8615484db09be58fc242b ]

During boot the Secure Boot Forbidden Signature Database, dbx,
is loaded into the blacklist keyring.  Systems booted with shim
have an equivalent Forbidden Signature Database called mokx.
Currently mokx is only used by shim and grub, the contents are
ignored by the kernel.

Add the ability to load mokx into the blacklist keyring during boot.

Signed-off-by: Eric Snowberg <eric.snowberg@oracle.com>
Suggested-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
cc: keyrings@vger.kernel.org
Link: https://lore.kernel.org/r/c33c8e3839a41e9654f41cc92c7231104931b1d7.camel@HansenPartnership.com/
Link: https://lore.kernel.org/r/20210122181054.32635-5-eric.snowberg@oracle.com/
Link: https://lore.kernel.org/r/161428674320.677100.12637282414018170743.stgit@warthog.procyon.org.uk/
Link: https://lore.kernel.org/r/161433313205.902181.2502803393898221637.stgit@warthog.procyon.org.uk/
Link: https://lore.kernel.org/r/161529607422.163428.13530426573612578854.stgit@warthog.procyon.org.uk/
Signed-off-by: Sasha Levin <sashal@kernel.org>
security/integrity/platform_certs/load_uefi.c