From: Stephan Mueller <smueller@chronox.de>
To: herbert@gondor.apana.org.au
Cc: boris.brezillon@free-electrons.com, linux-crypto@vger.kernel.org
Subject: [PATCH v4 0/3] SP800-38F / RFC3394 key wrapping
Date: Thu, 15 Oct 2015 09:05:48 +0200 [thread overview]
Message-ID: <5314960.0aGFzHXOSP@myon.chronox.de> (raw)
Hi,
Changes v4:
* make patch 3/3 standalone by incorporating and updating patch
https://lkml.org/lkml/2015/6/16/342
Changes v3:
* split patch for easier review
* add support for full SGL handling in decrypt by adding a "fast-forward"
function
* significant simplification of code and removal of one memcpy per round
* use of scatterwalk API throughout code and removal of self-written code
* perform a full CAVS test with all AES implementations available on X86
(C, assembler and AES-NI)
Changes v2:
* Turn kw() into a blkcipher as suggested by Herbert Xu.
* Drop the support for user provided IV to initialize encrypt or
for performing the verify step during decrypt.
Stephan Mueller (3):
crypto: add key wrapping block chaining mode
crypto: keywrap - enable compilation
crypto: keywrap - add testmgr support
crypto/Kconfig | 7 +
crypto/Makefile | 1 +
crypto/keywrap.c | 419 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
crypto/testmgr.c | 28 +++-
crypto/testmgr.h | 41 ++++++
5 files changed, 495 insertions(+), 1 deletion(-)
create mode 100644 crypto/keywrap.c
--
2.5.0
next reply other threads:[~2015-10-15 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 7:05 Stephan Mueller [this message]
2015-10-15 7:06 ` [PATCH v4 1/3] crypto: add key wrapping block chaining mode Stephan Mueller
2015-10-15 7:06 ` [PATCH v4 2/3] crypto: keywrap - enable compilation Stephan Mueller
2015-10-15 7:07 ` [PATCH v4 3/3] crypto: keywrap - add testmgr support Stephan Mueller
2015-10-15 7:11 ` Herbert Xu
2015-10-15 7:13 ` Stephan Mueller
2015-10-15 7:17 ` Herbert Xu
2015-10-15 10:10 ` Stephan Mueller
2015-10-15 10:17 ` Herbert Xu
2015-10-15 13:20 ` [PATCH v4 0/3] SP800-38F / RFC3394 key wrapping 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=5314960.0aGFzHXOSP@myon.chronox.de \
--to=smueller@chronox.de \
--cc=boris.brezillon@free-electrons.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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