From: David Sterba <dsterba@suse.com>
To: linux-crypto@vger.kernel.org
Cc: ard.biesheuvel@linaro.org, ebiggers@kernel.org,
David Sterba <dsterba@suse.com>
Subject: [PATCH v7 0/2] BLAKE2b generic implementation
Date: Thu, 24 Oct 2019 18:28:30 +0200 [thread overview]
Message-ID: <cover.1571934170.git.dsterba@suse.com> (raw)
The patchset adds blake2b reference implementation and test vectors.
V7:
Contents of include/crypto/blake2b.h moved to blake2b_generic.c, as the
exported constants or structures are not needed by anything as for now.
V1: https://lore.kernel.org/linux-crypto/cover.1569849051.git.dsterba@suse.com/
V2: https://lore.kernel.org/linux-crypto/e31c2030fcfa7f409b2c81adf8f179a8a55a584a.1570184333.git.dsterba@suse.com/
V3: https://lore.kernel.org/linux-crypto/e7f46def436c2c705c0b2cac3324f817efa4717d.1570715842.git.dsterba@suse.com/
V4: https://lore.kernel.org/linux-crypto/cover.1570812094.git.dsterba@suse.com/
V5: https://lore.kernel.org/linux-crypto/cover.1571043883.git.dsterba@suse.com/
V6: https://lore.kernel.org/linux-crypto/cover.1571788861.git.dsterba@suse.com/
David Sterba (2):
crypto: add blake2b generic implementation
crypto: add test vectors for blake2b
crypto/Kconfig | 17 ++
crypto/Makefile | 1 +
crypto/blake2b_generic.c | 435 +++++++++++++++++++++++++++++++++++++++
crypto/testmgr.c | 28 +++
crypto/testmgr.h | 307 +++++++++++++++++++++++++++
5 files changed, 788 insertions(+)
create mode 100644 crypto/blake2b_generic.c
--
2.23.0
next reply other threads:[~2019-10-24 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 16:28 David Sterba [this message]
2019-10-24 16:28 ` [PATCH v7 1/2] crypto: add blake2b generic implementation David Sterba
2019-10-25 5:15 ` Eric Biggers
2019-10-25 15:56 ` David Sterba
2019-10-24 16:28 ` [PATCH v7 2/2] crypto: add test vectors for blake2b David Sterba
2019-10-24 16:37 ` [PATCH v7 0/2] BLAKE2b generic implementation Ard Biesheuvel
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=cover.1571934170.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ebiggers@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.