The patch titled
SHA384 HMAC is broken
has been removed from the -mm tree. Its filename was
sha384-hmac-is-broken.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: SHA384 HMAC is broken
From: Andrew Donofrio <linuxbugzilla@xxxxxxxxxxx>
http://bugzilla.kernel.org/show_bug.cgi?id=7646
SHA384 and SHA512 share everything but the initial values and truncation of
the output, so their block sizes are the same. In the file
crypto/sha512.c, the SHA384_HMAC_BLOCK_SIZE is incorrectly #defined as 96,
when it should just be SHA512_HMAC_BLOCK_SIZE (i.e., 128). As it is now,
the kernel's SHA384 HMAC routine does not actually return "real" SHA384
HMACs.
Cc: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Cc: <stable@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
crypto/sha512.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN crypto/sha512.c~sha384-hmac-is-broken crypto/sha512.c
--- a/crypto/sha512.c~sha384-hmac-is-broken
+++ a/crypto/sha512.c
@@ -24,7 +24,7 @@
#define SHA384_DIGEST_SIZE 48
#define SHA512_DIGEST_SIZE 64
-#define SHA384_HMAC_BLOCK_SIZE 96
+#define SHA384_HMAC_BLOCK_SIZE SHA512_HMAC_BLOCK_SIZE
#define SHA512_HMAC_BLOCK_SIZE 128
struct sha512_ctx {
_
Patches currently in -mm which might be from linuxbugzilla@xxxxxxxxxxx are
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
