From: Adam Borowski <kilobyte@angband.pl>
To: David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Adam Borowski <kilobyte@angband.pl>, kernel test robot <lkp@intel.com>
Subject: [PATCH] certs: make system keyring depend on x509 parser
Date: Mon, 18 Jul 2022 15:50:34 +0200 [thread overview]
Message-ID: <20220718135034.51457-1-kilobyte@angband.pl> (raw)
In-Reply-To: <0f226def-baf9-d6b2-2ee3-f6fae7d675f1@leemhuis.info>
This code requires x509_load_certificate_list() to be built-in.
Fixes: 60050ffe3d77 ("certs: Move load_certificate_list() to be with the
asymmetric keys code")
Reported-by: kernel test robot <lkp@intel.com>
Link: https://lore.kernel.org/all/202206221515.DqpUuvbQ-lkp@intel.com/
Reported-by: Steven Rostedt <rostedt@goodmis.org>
Link: https://lore.kernel.org/all/20220712104554.408dbf42@gandalf.local.home/
Signed-off-by: Adam Borowski <kilobyte@angband.pl>
---
certs/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/certs/Kconfig b/certs/Kconfig
index 476755703cf8..bf9b511573d7 100644
--- a/certs/Kconfig
+++ b/certs/Kconfig
@@ -43,6 +43,7 @@ config SYSTEM_TRUSTED_KEYRING
bool "Provide system-wide ring of trusted keys"
depends on KEYS
depends on ASYMMETRIC_KEY_TYPE
+ depends on X509_CERTIFICATE_PARSER
help
Provide a system keyring to which trusted keys can be added. Keys in
the keyring are considered to be trusted. Keys may be added at will
--
2.36.1
prev parent reply other threads:[~2022-07-18 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 23:11 [PATCH] certs: make system keyring depend on x509 parser Adam Borowski
2022-07-18 6:55 ` Thorsten Leemhuis
2022-07-18 13:50 ` Adam Borowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220718135034.51457-1-kilobyte@angband.pl \
--to=kilobyte@angband.pl \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=regressions@leemhuis.info \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).