From: GlovePuppet <touched.by.his.noodley.appendage@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] Add HMAC-SHA-256
Date: Tue, 27 Oct 2020 08:43:31 -0700 (MST) [thread overview]
Message-ID: <1603813411162-0.post@n7.nabble.com> (raw)
Required by TPM2 Extended Auth, cloned from sha1.c
Signed-off-by: GlovePuppet <touched.by.his.noodley.appendage@gmail.com>
---
include/u-boot/sha256.h | 13 +++++++++++++
lib/sha256.c | 40 ++++++++++++++++++++++++++++++++++++++++
2 files changed, 53 insertions(+)
diff --git a/include/u-boot/sha256.h b/include/u-boot/sha256.h
index 9aa1251789..aa0e7f4418 100644
--- a/include/u-boot/sha256.h
+++ b/include/u-boot/sha256.h
@@ -22,4 +22,17 @@ void sha256_finish(sha256_context * ctx, uint8_t
digest[SHA256_SUM_LEN]);
void sha256_csum_wd(const unsigned char *input, unsigned int ilen,
unsigned char *output, unsigned int chunk_sz);
+/**
+ * \brief Output = HMAC-SHA-256( input buffer, hmac key )
+ *
+ * \param key HMAC secret key
+ * \param keylen length of the HMAC key
+ * \param input buffer holding the data
+ * \param ilen length of the input data
+ * \param output HMAC-SHA-256 result
+ */
+void sha256_hmac(const unsigned char *key, int keylen,
+ const unsigned char *input, unsigned int ilen,
+ unsigned char *output);
+
#endif /* _SHA256_H */
diff --git a/lib/sha256.c b/lib/sha256.c
index c1fe93de01..70123c1060 100644
--- a/lib/sha256.c
+++ b/lib/sha256.c
@@ -289,3 +289,43 @@ void sha256_csum_wd(const unsigned char *input,
unsigned int ilen,
sha256_finish(&ctx, output);
}
+
+/*
+ * Output = HMAC-SHA-256( input buffer, hmac key )
+ */
+void sha256_hmac(const unsigned char *key, int keylen,
+ const unsigned char *input, unsigned int ilen,
+ unsigned char *output)
+{
+ int i;
+ sha256_context ctx;
+ unsigned char k_ipad[64];
+ unsigned char k_opad[64];
+ unsigned char tmpbuf[32];
+
+ memset (k_ipad, 0x36, 64);
+ memset (k_opad, 0x5C, 64);
+
+ for (i = 0; i < keylen; i++) {
+ if (i >= 64)
+ break;
+
+ k_ipad[i] ^= key[i];
+ k_opad[i] ^= key[i];
+ }
+
+ sha256_starts (&ctx);
+ sha256_update (&ctx, k_ipad, 64);
+ sha256_update (&ctx, input, ilen);
+ sha256_finish (&ctx, tmpbuf);
+
+ sha256_starts (&ctx);
+ sha256_update (&ctx, k_opad, 64);
+ sha256_update (&ctx, tmpbuf, 32);
+ sha256_finish (&ctx, output);
+
+ memset (k_ipad, 0, 64);
+ memset (k_opad, 0, 64);
+ memset (tmpbuf, 0, 32);
+ memset (&ctx, 0, sizeof (sha256_context));
+}
--
2.17.1
--
Sent from: http://u-boot.10912.n7.nabble.com/
next reply other threads:[~2020-10-27 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 15:43 GlovePuppet [this message]
2020-10-28 7:28 ` [PATCH 1/2] Add HMAC-SHA-256 Wolfgang Denk
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=1603813411162-0.post@n7.nabble.com \
--to=touched.by.his.noodley.appendage@gmail.com \
--cc=u-boot@lists.denx.de \
/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