path: root/certs/Makefile
diff options
authorLinus Torvalds <>2022-06-21 12:13:53 -0500
committerLinus Torvalds <>2022-06-21 12:13:53 -0500
commit0273fd423b2fe10af96ff713273137c63a7736c0 (patch)
tree8c77927d7714223a95a57037d05e912c5cbac5e7 /certs/Makefile
parentff872b76b3d89a09a997cc45c133e4a3ddc12f90 (diff)
parent3cde3174eb910513d32a9ec8a9b95ea59be833df (diff)
Merge tag 'certs-20220621' of git://
Pull signature checking selftest from David Howells: "The signature checking code, as used by module signing, kexec, etc., is non-FIPS compliant as there is no selftest. For a kernel to be FIPS-compliant, signature checking would have to be tested before being used, and the box would need to panic if it's not available (probably reasonable as simply disabling signature checking would prevent you from loading any driver modules). Deal with this by adding a minimal test. This is split into two patches: the first moves load_certificate_list() to the same place as the X.509 code to make it more accessible internally; the second adds a selftest" * tag 'certs-20220621' of git:// certs: Add FIPS selftests certs: Move load_certificate_list() to be with the asymmetric keys code
Diffstat (limited to 'certs/Makefile')
1 files changed, 2 insertions, 2 deletions
diff --git a/certs/Makefile b/certs/Makefile
index a8d628fd5f7b..88a73b28d254 100644
--- a/certs/Makefile
+++ b/certs/Makefile
@@ -3,8 +3,8 @@
# Makefile for the linux kernel signature checking certificates.
-obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o common.o
-obj-$(CONFIG_SYSTEM_BLACKLIST_KEYRING) += blacklist.o common.o
+obj-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += system_keyring.o system_certificates.o
obj-$(CONFIG_SYSTEM_REVOCATION_LIST) += revocation_certificates.o