From: clabbe.montjoie@gmail.com (Corentin Labbe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/9] crypto: add hmac IPAD/OPAD constant
Date: Fri, 19 May 2017 08:53:23 +0200 [thread overview]
Message-ID: <20170519065331.27670-2-clabbe.montjoie@gmail.com> (raw)
In-Reply-To: <20170519065331.27670-1-clabbe.montjoie@gmail.com>
Many HMAC users directly use directly 0x36/0x5c values.
It's better with crypto to use a name instead of directly some crypto
constant.
This patch simply add HMAC_IPAD_VALUE/HMAC_OPAD_VALUE defines in a new
include file "crypto/hmac.h" and use them in crypto/hmac.c
Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
---
crypto/hmac.c | 5 +++--
include/crypto/hmac.h | 7 +++++++
2 files changed, 10 insertions(+), 2 deletions(-)
create mode 100644 include/crypto/hmac.h
diff --git a/crypto/hmac.c b/crypto/hmac.c
index 72e38c098bb3..92871dc2a63e 100644
--- a/crypto/hmac.c
+++ b/crypto/hmac.c
@@ -16,6 +16,7 @@
*
*/
+#include <crypto/hmac.h>
#include <crypto/internal/hash.h>
#include <crypto/scatterwalk.h>
#include <linux/err.h>
@@ -74,8 +75,8 @@ static int hmac_setkey(struct crypto_shash *parent,
memcpy(opad, ipad, bs);
for (i = 0; i < bs; i++) {
- ipad[i] ^= 0x36;
- opad[i] ^= 0x5c;
+ ipad[i] ^= HMAC_IPAD_VALUE;
+ opad[i] ^= HMAC_OPAD_VALUE;
}
return crypto_shash_init(shash) ?:
diff --git a/include/crypto/hmac.h b/include/crypto/hmac.h
new file mode 100644
index 000000000000..ef09f7938204
--- /dev/null
+++ b/include/crypto/hmac.h
@@ -0,0 +1,7 @@
+#ifndef _CRYPTO_HMAC_H
+#define _CRYPTO_HMAC_H
+
+#define HMAC_IPAD_VALUE 0x36
+#define HMAC_OPAD_VALUE 0x5c
+
+#endif /* _CRYPTO_HMAC_H */
--
2.13.0
next prev parent reply other threads:[~2017-05-19 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 6:53 [PATCH v2 0/9] crypto: add HMAC IPAD/OPAD constant Corentin Labbe
2017-05-19 6:53 ` Corentin Labbe [this message]
2017-05-19 6:53 ` [PATCH v2 2/9] crypto: brcm - Use " Corentin Labbe
2017-05-19 6:53 ` [PATCH v2 3/9] crypto: ixp4xx " Corentin Labbe
2017-05-19 6:53 ` [PATCH v2 4/9] crypto: marvell " Corentin Labbe
2017-05-19 9:17 ` Boris Brezillon
2017-05-19 6:53 ` [PATCH v2 5/9] crypto: mv_cesa " Corentin Labbe
2017-05-19 6:53 ` [PATCH v2 6/9] crypto: omap-sham " Corentin Labbe
2017-05-19 6:53 ` [PATCH v2 7/9] crypto: qat " Corentin Labbe
2017-05-19 6:53 ` [PATCH v2 8/9] crypto: mediatek " Corentin Labbe
2017-05-19 9:11 ` Matthias Brugger
2017-05-19 6:53 ` [PATCH v2 9/9] crypto: ccp " Corentin Labbe
2017-05-19 20:32 ` Gary R Hook
2017-05-23 5:03 ` [PATCH v2 0/9] crypto: add HMAC " 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=20170519065331.27670-2-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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