summaryrefslogtreecommitdiff
path: root/crypto/asymmetric_keys
diff options
context:
space:
mode:
authorThomas Weißschuh <linux@weissschuh.net>2023-01-09 23:59:43 +0000
committerJarkko Sakkinen <jarkko@kernel.org>2023-02-13 10:11:20 +0200
commitc95e8f6fd157b45ef0685c221931561e943e82da (patch)
tree947ea6033cc050a4c3c21ca02e548ff5931b4e2e /crypto/asymmetric_keys
parent6c1976addf3623e979b7a954e216004d559bcb42 (diff)
certs: don't try to update blacklist keys
When the same key is blacklisted repeatedly logging at pr_err() level is excessive as no functionality is impaired. When these duplicates are provided by buggy firmware there is nothing the user can do to fix the situation. Instead of spamming the bootlog with errors we use a warning that can still be seen by OEMs when testing their firmware. Link: https://lore.kernel.org/all/c8c65713-5cda-43ad-8018-20f2e32e4432@t-8ch.de/ Link: https://lore.kernel.org/all/20221104014704.3469-1-linux@weissschuh.net/ Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> Tested-by: Paul Menzel <pmenzel@molgen.mpg.de> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
Diffstat (limited to 'crypto/asymmetric_keys')
0 files changed, 0 insertions, 0 deletions