From: "Adrian-Ken Rüegsegger" <rueegsegger@swiss-it.ch>
To: linux-crypto@vger.kernel.org
Cc: linux-crypto@ml.breakpoint.cc
Subject: tcrypt: hmac test with keys > blocksize fail
Date: Sat, 03 May 2008 02:10:34 +0200 [thread overview]
Message-ID: <481BAD7A.3010003@swiss-it.ch> (raw)
Hi,
using the cryptodev-2.6 tree I noticed that the hmac tests that have
keys larger than blocksize for md5 and the various sha algorithms all
fail (tcrypt mode=10[0-5]). The other tests seem to pass just fine.
The issue seems to have come from commit
de224c309b5631bdaae3fcd6880cfb93b52f5a53.
I have tested 48c8949ea8460216783dd33640121187b9531b60 which does not
contain this bug. It's just before the various tcrypt-changes from
Sebastian Siewior.
-Adrian
next reply other threads:[~2008-05-03 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 0:10 Adrian-Ken Rüegsegger [this message]
2008-05-03 6:21 ` tcrypt: hmac test with keys > blocksize fail Sebastian Siewior
2008-05-03 11:44 ` Adrian-Ken Rüegsegger
2008-05-04 18:56 ` Sebastian Siewior
2008-05-06 10:28 ` Herbert Xu
2008-05-06 20:53 ` Adrian-Ken Rüegsegger
2008-05-14 7:27 ` Sebastian Siewior
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=481BAD7A.3010003@swiss-it.ch \
--to=rueegsegger@swiss-it.ch \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@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