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 0/4] crypto: Key Derivation Function (SP800-108)
Date: Tue, 09 Aug 2016 14:27:18 +0200 [thread overview]
Message-ID: <2808589.gm6f519sFh@positron.chronox.de> (raw)
Hi,
this patch set implements all three key derivation functions defined in
SP800-108.
The implementation is provided as a template for random number generators,
since a KDF can be considered a form of deterministic RNG where the key
material is used as a seed.
With the KDF implemented as a template, all types of keyed and
non-keyed hashes can be utilized, including HMAC and CMAC. The testmgr
tests are derived from publicly available test vectors from NIST.
The KDF are all tested with a complete round of CAVS testing on 32 and 64 bit.
The patch set introduces an extension to the kernel crypto API in the first
patch by adding a template handling for random number generators based on the
same logic as for keyed hashes.
Changes v5:
* move rng_instance and __crypto_rng_alg into rng.c
Changes v4:
* removal of the check that src and dst buffers are not the same from the KDF
implementations as requested by Herbert
* implement and use new free API in the RNG instance handling as requested
by Herbert
* move the instance handling code from include/crypto/rng.h to
include/crypto/internal/rng.h
Changes v3:
* port testmgr patch to current cryptodev-2.6 tree
* add non-keyed KDF references to testmgr.c
Changes v2:
* port to 4.7-rc1
Stephan Mueller (4):
crypto: add template handling for RNGs
crypto: kdf - add known answer tests
crypto: kdf - SP800-108 Key Derivation Function
crypto: kdf - enable compilation
crypto/Kconfig | 7 +
crypto/Makefile | 1 +
crypto/kdf.c | 508 ++++++++++++++++++++++++++++++++++++++++++
crypto/rng.c | 44 ++++
crypto/testmgr.c | 226 +++++++++++++++++++
crypto/testmgr.h | 110 +++++++++
include/crypto/internal/rng.h | 26 +++
7 files changed, 922 insertions(+)
create mode 100644 crypto/kdf.c
--
2.7.4
next 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 Stephan Mueller [this message]
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 ` [PATCH v5 4/4] crypto: kdf - enable compilation Stephan Mueller
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=2808589.gm6f519sFh@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