From: David Howells <dhowells@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: dhowells@redhat.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: NIST FIPS test vector failures
Date: Tue, 20 Jan 2026 15:00:40 +0000 [thread overview]
Message-ID: <1176724.1768921240@warthog.procyon.org.uk> (raw)
In-Reply-To: <20260119185125.GA11957@sol>
Actually, one external test (tcId 35) does actually work. It turns out that
that's the only expected-to-pass test with an empty context string that
doesn't have an external mu or prehashing. So I've taken that one as a test
case.
David
next prev parent reply other threads:[~2026-01-20 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 16:48 NIST FIPS test vector failures David Howells
2026-01-19 17:09 ` David Howells
2026-01-19 18:51 ` Eric Biggers
2026-01-20 15:00 ` David Howells [this message]
2026-01-20 15:04 ` Python script to generate X509/CMS from NIST testcases David Howells
2026-01-20 15:42 ` Stephan Mueller
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=1176724.1768921240@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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