From: Stephan Mueller <smueller@chronox.de>
To: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Cc: aquini@redhat.com, jeremy.wayne.powell@gmail.com,
clemens@ladisch.de, pwalten@au1.ibm.com, joe@perches.com
Subject: [PATCH v7 3/6] DRBG kernel configuration options
Date: Wed, 21 May 2014 06:20:38 +0200 [thread overview]
Message-ID: <1420904.WdM3jEvtHL@myon.chronox.de> (raw)
In-Reply-To: <16102625.1uoi9eJz6k@myon.chronox.de>
The different DRBG types of CTR, Hash, HMAC can be enabled or disabled
at compile time. At least one DRBG type shall be selected.
The default is the HMAC DRBG as its code base is smallest.
Signed-off-by: Stephan Mueller <smueller@chronox.de>
---
crypto/Kconfig | 36 +++++++++++++++++++++++++++++++++++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index ce4012a..c9c1cd9 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -23,7 +23,7 @@ comment "Crypto core or helper"
config CRYPTO_FIPS
bool "FIPS 200 compliance"
- depends on CRYPTO_ANSI_CPRNG && !CRYPTO_MANAGER_DISABLE_TESTS
+ depends on (CRYPTO_ANSI_CPRNG || CRYTPO_DRBG) && !CRYPTO_MANAGER_DISABLE_TESTS
help
This options enables the fips boot option which is
required if you want to system to operate in a FIPS 200
@@ -1380,6 +1380,40 @@ config CRYPTO_ANSI_CPRNG
ANSI X9.31 A.2.4. Note that this option must be enabled if
CRYPTO_FIPS is selected
+menuconfig CRYTPO_DRBG
+ tristate "NIST SP800-90A DRBG"
+ depends on CRYPTO
+ select CRYPTO_RNG
+ help
+ NIST SP800-90A compliant DRBG. In the following submenu, one or
+ more of the DRBG types must be selected.
+
+if CRYTPO_DRBG
+
+config CRYPTO_DRBG_HMAC
+ bool "Enable HMAC DRBG"
+ default y
+ depends on CRYTPO_DRBG
+ select CRYPTO_HMAC
+ help
+ Enable the HMAC DRBG variant as defined in NIST SP800-90A.
+
+config CRYPTO_DRBG_HASH
+ bool "Enable Hash DRBG"
+ depends on CRYTPO_DRBG
+ select CRYPTO_HASH
+ help
+ Enable the Hash DRBG variant as defined in NIST SP800-90A.
+
+config CRYPTO_DRBG_CTR
+ bool "Enable CTR DRBG"
+ depends on CRYTPO_DRBG
+ select CRYPTO_AES
+ help
+ Enable the CTR DRBG variant as defined in NIST SP800-90A.
+
+endif #CRYTPO_DRBG
+
config CRYPTO_USER_API
tristate
--
1.9.0
next prev parent reply other threads:[~2014-05-21 4:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 4:18 [PATCH v7 0/6] SP800-90A Deterministic Random Bit Generator Stephan Mueller
2014-05-21 4:18 ` [PATCH v7 1/6] " Stephan Mueller
2014-05-21 20:17 ` Stephan Mueller
2014-05-23 21:10 ` Herbert Xu
2014-05-26 5:44 ` Stephan Mueller
2014-05-21 4:19 ` [PATCH v7 2/6] header file for DRBG Stephan Mueller
2014-05-21 4:20 ` Stephan Mueller [this message]
2014-05-21 4:21 ` [PATCH v7 4/6] compile the DRBG code Stephan Mueller
2014-05-21 4:21 ` [PATCH v7 5/6] DRBG testmgr test vectors Stephan Mueller
2014-05-21 4:22 ` [PATCH v7 6/6] Add DRBG test code to testmgr Stephan Mueller
2014-05-23 21:14 ` [PATCH v7 0/6] SP800-90A Deterministic Random Bit Generator Herbert Xu
2014-05-26 5:42 ` Stephan Mueller
2014-05-30 9:05 ` Herbert Xu
2014-05-30 10:08 ` Stephan Mueller
2014-05-30 10:52 ` Herbert Xu
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=1420904.WdM3jEvtHL@myon.chronox.de \
--to=smueller@chronox.de \
--cc=aquini@redhat.com \
--cc=clemens@ladisch.de \
--cc=jeremy.wayne.powell@gmail.com \
--cc=joe@perches.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pwalten@au1.ibm.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
all inboxes | Powered by JetHome®