From: Jarod Wilson <jarod@redhat.com>
To: linux-crypto@vger.kernel.org
Cc: Herbert Xu <herbert@gondor.hengli.com.au>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] crypto/testmgr: add xts-aes-256 self-test
Date: Wed, 25 May 2011 16:46:30 -0400 [thread overview]
Message-ID: <4DDD6AA6.30800@redhat.com> (raw)
In-Reply-To: <1306348377-14494-1-git-send-email-jarod@redhat.com>
Jarod Wilson wrote:
> FIPS compliance requires a known-answer self-test for all approved cipher and
> mode combinations, for all valid key sizes. Presently, there are only
> self-tests for xts-aes-128. This adds a 256-bit one, pulled from the same
> reference document, which should satisfy the requirement.
Oh hell. v2 coming in a bit after I verify its actually really still
functional with the new vector added. I forgot to update
AES_XTS_ENC_TEST_VECTORS and AES_XTS_DEC_TEST_VECTORS to match, so the
new vector wasn't being run.
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2011-05-25 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 18:32 [PATCH] crypto/testmgr: add xts-aes-256 self-test Jarod Wilson
2011-05-25 20:46 ` Jarod Wilson [this message]
2011-05-27 15:59 ` [PATCH v2] [crypto] testmgr: " Jarod Wilson
2011-05-31 5:24 ` 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=4DDD6AA6.30800@redhat.com \
--to=jarod@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.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;
as well as URLs for NNTP newsgroup(s).