From: Thorsten Berger <thorsten.berger@rub.de>
To: linux-kbuild@vger.kernel.org
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
deltaone@debian.org, phayax@gmail.com,
Eugene Groshev <eugene.groshev@gmail.com>,
Sarah Nadi <nadi@ualberta.ca>, Mel Gorman <mgorman@suse.de>,
"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: [RFC 12/12] Simplify dependencies for MODULE_SIG_KEY_TYPE_RSA & MODULE_SIG_KEY_TYPE_ECDSA
Date: Wed, 20 Oct 2021 11:49:46 +0200 [thread overview]
Message-ID: <fdbbc1a6-5806-85a0-5b37-206558facaab@rub.de> (raw)
In-Reply-To: <c2b36549-5c9e-2314-bc68-b81b7c77a561@rub.de>
Co-developed-by: Patrick Franz <deltaone@debian.org>
Signed-off-by: Patrick Franz <deltaone@debian.org>
Co-developed-by: Ibrahim Fayaz <phayax@gmail.com>
Signed-off-by: Ibrahim Fayaz <phayax@gmail.com>
Reviewed-by: Luis Chamberlain <mcgrof@suse.com>
Tested-by: Evgeny Groshev <eugene.groshev@gmail.com>
Suggested-by: Sarah Nadi <nadi@ualberta.ca>
Suggested-by: Thorsten Berger <thorsten.berger@rub.de>
Signed-off-by: Thorsten Berger <thorsten.berger@rub.de>
---
certs/Kconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/certs/Kconfig b/certs/Kconfig
index ae7f2e876a31..f69c92e5bc30 100644
--- a/certs/Kconfig
+++ b/certs/Kconfig
@@ -17,6 +17,7 @@ config MODULE_SIG_KEY
choice
prompt "Type of module signing key to be generated"
+ depends on MODULE_SIG || (IMA_APPRAISE_MODSIG && MODULES)
default MODULE_SIG_KEY_TYPE_RSA
help
The type of module signing key type to generate. This option
@@ -24,14 +25,12 @@ choice
config MODULE_SIG_KEY_TYPE_RSA
bool "RSA"
- depends on MODULE_SIG || (IMA_APPRAISE_MODSIG && MODULES)
help
Use an RSA key for module signing.
config MODULE_SIG_KEY_TYPE_ECDSA
bool "ECDSA"
select CRYPTO_ECDSA
- depends on MODULE_SIG || (IMA_APPRAISE_MODSIG && MODULES)
help
Use an elliptic curve key (NIST P384) for module signing. Consider
using a strong hash like sha256 or sha384 for hashing modules.
--
2.33.0
next prev parent reply other threads:[~2021-10-20 9:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 9:32 [RFC 0/12] kconfig: add support for conflict resolution Thorsten Berger
2021-10-20 9:35 ` [RFC 01/12] Add picosat.h Thorsten Berger
2021-10-20 15:54 ` Luis Chamberlain
2021-10-20 9:36 ` [RFC 02/12] Add picosat.c (1/3) Thorsten Berger
2021-10-20 9:37 ` [RFC 03/12] Add picosat.c (2/3) Thorsten Berger
2021-10-20 9:38 ` [RFC 04/12] Add picosat.c (3/3) Thorsten Berger
2021-10-20 9:40 ` [RFC 05/12] Add definitions Thorsten Berger
2021-10-20 9:41 ` [RFC 06/12] Add files for building constraints Thorsten Berger
2021-10-20 9:43 ` [RFC 07/12] Add files for handling expressions Thorsten Berger
2021-10-20 9:44 ` [RFC 08/12] Add files for RangeFix Thorsten Berger
2021-10-20 9:45 ` [RFC 09/12] Add files with utility functions Thorsten Berger
2021-10-20 9:46 ` [RFC 10/12] Add tools Thorsten Berger
2021-10-20 9:48 ` [RFC 11/12] Add xconfig-modifications Thorsten Berger
2021-10-20 9:49 ` Thorsten Berger [this message]
2021-10-28 2:48 ` [RFC 12/12] Simplify dependencies for MODULE_SIG_KEY_TYPE_RSA & MODULE_SIG_KEY_TYPE_ECDSA Masahiro Yamada
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=fdbbc1a6-5806-85a0-5b37-206558facaab@rub.de \
--to=thorsten.berger@rub.de \
--cc=deltaone@debian.org \
--cc=eugene.groshev@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=mgorman@suse.de \
--cc=nadi@ualberta.ca \
--cc=phayax@gmail.com \
/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