From: Stephan Mueller <smueller@chronox.de>
To: herbert@gondor.apana.org.au
Cc: mathew.j.martineau@linux.intel.com, dhowells@redhat.com,
linux-crypto@vger.kernel.org, keyrings@vger.kernel.org
Subject: [PATCH v5 4/4] crypto: kdf - enable compilation
Date: Tue, 09 Aug 2016 14:28:57 +0200 [thread overview]
Message-ID: <2461264.8cTuJkSQam@positron.chronox.de> (raw)
In-Reply-To: <2808589.gm6f519sFh@positron.chronox.de>
Include KDF into Kconfig and Makefile for compilation.
Signed-off-by: Stephan Mueller <smueller@chronox.de>
---
crypto/Kconfig | 7 +++++++
crypto/Makefile | 1 +
2 files changed, 8 insertions(+)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 84d7148..16f3221 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -372,6 +372,13 @@ config CRYPTO_KEYWRAP
Support for key wrapping (NIST SP800-38F / RFC3394) without
padding.
+config CRYPTO_KDF
+ tristate "Key Derivation Function (SP800-108)"
+ select CRYPTO_RNG
+ help
+ Support for KDF compliant to SP800-108. All three types of
+ KDF specified in SP800-108 are implemented.
+
comment "Hash modes"
config CRYPTO_CMAC
diff --git a/crypto/Makefile b/crypto/Makefile
index 99cc64a..9022280 100644
--- a/crypto/Makefile
+++ b/crypto/Makefile
@@ -80,6 +80,7 @@ obj-$(CONFIG_CRYPTO_LRW) += lrw.o
obj-$(CONFIG_CRYPTO_XTS) += xts.o
obj-$(CONFIG_CRYPTO_CTR) += ctr.o
obj-$(CONFIG_CRYPTO_KEYWRAP) += keywrap.o
+obj-$(CONFIG_CRYPTO_KDF) += kdf.o
obj-$(CONFIG_CRYPTO_GCM) += gcm.o
obj-$(CONFIG_CRYPTO_CCM) += ccm.o
obj-$(CONFIG_CRYPTO_CHACHA20POLY1305) += chacha20poly1305.o
--
2.7.4
prev parent reply other threads:[~2016-08-09 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 12:27 [PATCH v5 0/4] crypto: Key Derivation Function (SP800-108) Stephan Mueller
2016-08-09 12:27 ` [PATCH v5 1/4] crypto: add template handling for RNGs Stephan Mueller
2016-08-09 12:28 ` [PATCH v5 2/4] crypto: kdf - add known answer tests Stephan Mueller
2016-08-09 12:28 ` [PATCH v5 3/4] crypto: kdf - SP800-108 Key Derivation Function Stephan Mueller
2016-08-16 8:57 ` Herbert Xu
2016-08-16 9:11 ` Stephan Mueller
2016-08-16 9:13 ` Herbert Xu
2016-08-16 9:25 ` Stephan Mueller
2016-08-16 9:26 ` Herbert Xu
2016-08-09 12:28 ` Stephan Mueller [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=2461264.8cTuJkSQam@positron.chronox.de \
--to=smueller@chronox.de \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.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