Thomas Weißschuh 06b53b0294 certs: make blacklisted hash available in klog ... One common situation triggering this log statement are duplicate hashes reported by the system firmware. These duplicates should be removed from the firmware. Without logging the blacklisted hash triggering the issue however the users can not report it properly to the firmware vendors and the firmware vendors can not easily see which specific hash is duplicated. While changing the log message also use the dedicated ERR_PTR format placeholder for the returned error value. Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>		2023-02-13 10:11:20 +02:00
..
.gitignore
blacklist.c	certs: make blacklisted hash available in klog	2023-02-13 10:11:20 +02:00
blacklist.h
blacklist_hashes.c	certs: unify blacklist_hashes.c and blacklist_nohashes.c	2022-07-27 21:17:59 +09:00
check-blacklist-hashes.awk	certs: move scripts/check-blacklist-hashes.awk to certs/	2022-07-27 21:17:59 +09:00
default_x509.genkey
extract-cert.c
Kconfig	certs: make system keyring depend on built-in x509 parser	2022-09-24 04:31:18 +09:00
Makefile	certs: Fix build error when PKCS#11 URI contains semicolon	2023-01-31 17:53:01 +09:00
revocation_certificates.S
system_certificates.S
system_keyring.c	certs: Move load_certificate_list() to be with the asymmetric keys code	2022-06-21 16:05:06 +01:00