From: "Adrian-Ken Rüegsegger" <rueegsegger@swiss-it.ch>
To: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Cc: linux-crypto@vger.kernel.org
Subject: Re: tcrypt: hmac test with keys > blocksize fail
Date: Sat, 03 May 2008 13:44:41 +0200 [thread overview]
Message-ID: <481C5029.9040406@swiss-it.ch> (raw)
In-Reply-To: <20080503062113.GB30328@Chamillionaire.breakpoint.cc>
Sebastian Siewior wrote:
> * Adrian-Ken R?egsegger | 2008-05-03 02:10:34 [+0200]:
>
>> Hi,
> Hi Adrian-Ken,
Hello Sebastian,
>> 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.
> Is this a bisect result?
No, this was a guess of mine, since I tested the two revisions just
prior and after the three tcrypt-commits from you. I did a full bisect
and the actual guilty commit is:
[562954d5e01d08154cf15c7e12e6e9ec803f50f7] [CRYPTO] tcrypt: Change the
usage of the test vectors
>> I have tested 48c8949ea8460216783dd33640121187b9531b60 which does not
>> contain this bug. It's just before the various tcrypt-changes from
>> Sebastian Siewior.
> I tested it with tcrypt mode=0 what covers 100-105 but it may slip
> through. I will look into this later.
As I mentioned, it's only the hmac tests with keys larger than blocksize
that fail.
Additionaly I just saw, that ecb(des) encryption test nr 5 passes but it
seems that the setkey operation fails with:
setkey() failed flags=100100
-Adrian
next prev parent reply other threads:[~2008-05-03 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 0:10 tcrypt: hmac test with keys > blocksize fail Adrian-Ken Rüegsegger
2008-05-03 6:21 ` Sebastian Siewior
2008-05-03 11:44 ` Adrian-Ken Rüegsegger [this message]
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=481C5029.9040406@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