From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
ralf@linux-mips.org, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au, aaro.koskinen@iki.fi
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
LABBE Corentin <clabbe.montjoie@gmail.com>,
linux-crypto@vger.kernel.org, sparclinux@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 1/6] crypto: md5: add MD5 initial vectors
Date: Sun, 17 May 2015 12:54:12 +0200 [thread overview]
Message-ID: <1431860057-5232-1-git-send-email-clabbe.montjoie@gmail.com> (raw)
This patch simply adds the MD5 IV in the md5 header.
Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
---
include/crypto/md5.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/crypto/md5.h b/include/crypto/md5.h
index 65f299b..146af82 100644
--- a/include/crypto/md5.h
+++ b/include/crypto/md5.h
@@ -8,6 +8,11 @@
#define MD5_BLOCK_WORDS 16
#define MD5_HASH_WORDS 4
+#define MD5_H0 0x67452301UL
+#define MD5_H1 0xefcdab89UL
+#define MD5_H2 0x98badcfeUL
+#define MD5_H3 0x10325476UL
+
struct md5_state {
u32 hash[MD5_HASH_WORDS];
u32 block[MD5_BLOCK_WORDS];
--
2.3.6
next reply other threads:[~2015-05-17 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 10:54 LABBE Corentin [this message]
2015-05-17 10:54 ` [PATCH 2/6] crypto: md5: use md5 IV MD5_HX instead of their raw value LABBE Corentin
2015-05-17 10:54 ` [PATCH 3/6] crypto: powerpc/md5: " LABBE Corentin
2015-05-17 10:54 ` [PATCH 4/6] crypto: sparc/md5: " LABBE Corentin
2015-05-17 10:54 ` [PATCH 5/6] crypto: n2: " LABBE Corentin
2015-05-17 10:54 ` [PATCH 6/6] crypto: octeon: " LABBE Corentin
2015-05-18 4:25 ` [PATCH 1/6] crypto: md5: add MD5 initial vectors 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=1431860057-5232-1-git-send-email-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=sparclinux@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 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).