From: Milan Broz <gmazyland@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [v2 PATCH] crypto: wp512 - Use API partial block handling
Date: Fri, 20 Jun 2025 10:52:49 +0200 [thread overview]
Message-ID: <953e81bc-edbc-456b-8276-536d313ab220@gmail.com> (raw)
In-Reply-To: <aFUd1upBNhEM1KfG@gondor.apana.org.au>
On 6/20/25 10:37 AM, Herbert Xu wrote:
> On Fri, Jun 20, 2025 at 10:10:53AM +0200, Milan Broz wrote:
>>
>> Now I get wrong data instead of fail (both on 32bit and 64bit).
>> Patch just applied over today's Linus' tree
>>
>> ...
>> PBKDF vector 20 pbkdf2-whirlpool [FAILED]
>> got: 58 55 1e ef 29 40 d6 a2 f0 59 e0 d9 4a 50 c5 df 01 25 be ee 27 5b 35 47 6d 37 38 13 0f e0 da 29
>> want: 9c 1c 74 f5 88 26 e7 6a 53 58 f4 0c 39 e7 80 89 07 c0 31 19 9a 50 a2 48 f1 d9 fe 78 64 e5 84 50
>> PBKDF test failed.
>>
>> (Whirlpool is translated to wp512 in the crypto backend and despite it is a quite rare use, some people
>> used if for LUKS PBKDF2. Actually the whole vector test was reaction to wrong Whirlpool implementation
>> in gcrypt years ago. It apparently can find breakage even today :-)
>
> Oops, I forgot to increment the hash length for the final partial
> update :)
It s still failing for me for that userspace crypt API.
Milan
next prev parent reply other threads:[~2025-06-20 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 21:18 Failure in HMAC with Whirlpool hash in 6.16-rc2 Milan Broz
2025-06-20 4:19 ` Herbert Xu
2025-06-20 5:47 ` [PATCH] crypto: wp512 - Use API partial block handling Herbert Xu
2025-06-20 8:10 ` Milan Broz
2025-06-20 8:37 ` [v2 PATCH] " Herbert Xu
2025-06-20 8:52 ` Milan Broz [this message]
2025-06-20 12:15 ` [v3 " Herbert Xu
2025-06-20 13:22 ` Milan Broz
2025-06-21 3:06 ` 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=953e81bc-edbc-456b-8276-536d313ab220@gmail.com \
--to=gmazyland@gmail.com \
--cc=herbert@gondor.apana.org.au \
--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