From: Antoine Tenart <antoine.tenart@bootlin.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: Antoine Tenart <antoine.tenart@bootlin.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, maxime.chevallier@bootlin.com,
gregory.clement@bootlin.com, miquel.raynal@bootlin.com,
nadavh@marvell.com, oferh@marvell.com, igall@marvell.com
Subject: [PATCH 07/10] crypto: sha512_generic - add a sha384 0-length pre-computed hash
Date: Tue, 29 May 2018 14:13:49 +0200 [thread overview]
Message-ID: <20180529121352.19490-8-antoine.tenart@bootlin.com> (raw)
In-Reply-To: <20180529121352.19490-1-antoine.tenart@bootlin.com>
This patch adds the sha384 pre-computed 0-length hash so that device
drivers can use it when an hardware engine does not support computing a
hash from a 0 length input.
Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>
---
crypto/sha512_generic.c | 10 ++++++++++
include/crypto/sha.h | 2 ++
2 files changed, 12 insertions(+)
diff --git a/crypto/sha512_generic.c b/crypto/sha512_generic.c
index 439723d9273e..0b805d03b5e5 100644
--- a/crypto/sha512_generic.c
+++ b/crypto/sha512_generic.c
@@ -23,6 +23,16 @@
#include <asm/byteorder.h>
#include <asm/unaligned.h>
+const u8 sha384_zero_message_hash[SHA384_DIGEST_SIZE] = {
+ 0x38, 0xb0, 0x60, 0xa7, 0x51, 0xac, 0x96, 0x38,
+ 0x4c, 0xd9, 0x32, 0x7e, 0xb1, 0xb1, 0xe3, 0x6a,
+ 0x21, 0xfd, 0xb7, 0x11, 0x14, 0xbe, 0x07, 0x43,
+ 0x4c, 0x0c, 0xc7, 0xbf, 0x63, 0xf6, 0xe1, 0xda,
+ 0x27, 0x4e, 0xde, 0xbf, 0xe7, 0x6f, 0x65, 0xfb,
+ 0xd5, 0x1a, 0xd2, 0xf1, 0x48, 0x98, 0xb9, 0x5b
+};
+EXPORT_SYMBOL_GPL(sha384_zero_message_hash);
+
const u8 sha512_zero_message_hash[SHA512_DIGEST_SIZE] = {
0xcf, 0x83, 0xe1, 0x35, 0x7e, 0xef, 0xb8, 0xbd,
0xf1, 0x54, 0x28, 0x50, 0xd6, 0x6d, 0x80, 0x07,
diff --git a/include/crypto/sha.h b/include/crypto/sha.h
index 799f071b93df..8a46202b1857 100644
--- a/include/crypto/sha.h
+++ b/include/crypto/sha.h
@@ -71,6 +71,8 @@ extern const u8 sha224_zero_message_hash[SHA224_DIGEST_SIZE];
extern const u8 sha256_zero_message_hash[SHA256_DIGEST_SIZE];
+extern const u8 sha384_zero_message_hash[SHA384_DIGEST_SIZE];
+
extern const u8 sha512_zero_message_hash[SHA512_DIGEST_SIZE];
struct sha1_state {
--
2.17.0
next prev parent reply other threads:[~2018-05-29 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 12:13 [PATCH 00/10] crypto: inside-secure - sha512/384 support Antoine Tenart
2018-05-29 12:13 ` [PATCH 01/10] crypto: inside-secure - use the error handler for invalidation requests Antoine Tenart
2018-05-29 12:13 ` [PATCH 02/10] crypto: inside-secure - improve the counter computation Antoine Tenart
2018-05-29 12:13 ` [PATCH 03/10] crypto: sha512_generic - add a sha512 0-length pre-computed hash Antoine Tenart
2018-05-29 12:13 ` [PATCH 04/10] crypto: inside-secure - sha512 support Antoine Tenart
2018-05-29 12:13 ` [PATCH 05/10] crypto: inside-secure - hmac(sha512) support Antoine Tenart
2018-05-29 12:13 ` [PATCH 06/10] crypto: inside-secure - authenc(hmac(sha512),cbc(aes)) support Antoine Tenart
2018-05-29 12:13 ` Antoine Tenart [this message]
2018-05-29 12:13 ` [PATCH 08/10] crypto: inside-secure - sha384 support Antoine Tenart
2018-05-29 12:13 ` [PATCH 09/10] crypto: inside-secure - hmac(sha384) support Antoine Tenart
2018-05-29 12:13 ` [PATCH 10/10] crypto: inside-secure - authenc(hmac(sha384),cbc(aes)) support Antoine Tenart
2018-06-22 15:22 ` [PATCH 00/10] crypto: inside-secure - sha512/384 support 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=20180529121352.19490-8-antoine.tenart@bootlin.com \
--to=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=gregory.clement@bootlin.com \
--cc=herbert@gondor.apana.org.au \
--cc=igall@marvell.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=nadavh@marvell.com \
--cc=oferh@marvell.com \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).