From: Jarod Wilson <jarod@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH v2] crypto: add ctr(aes) test vectors
Date: Wed, 6 May 2009 08:51:33 -0400 [thread overview]
Message-ID: <200905060851.34129.jarod@redhat.com> (raw)
In-Reply-To: <20090506093021.GA31073@gondor.apana.org.au>
On Wednesday 06 May 2009 05:30:21 Herbert Xu wrote:
> On Tue, May 05, 2009 at 10:42:58AM -0400, Jarod Wilson wrote:
> >
> > Now with multi-block test vectors, all from SP800-38A, Appendix F.5.
> > Also added ctr(aes) to case 10 in tcrypt.
> >
> > Quickly smoke-tested in fips mode, got back "alg_test: alg
> > ctr(aes-x86_64) (ctr(aes)) self-test passed".
> >
> > Signed-off-by: Jarod Wilson <jarod@redhat.com>
>
> It didn't build because you forgot to change the RFC3686 dec
> vector name. I've fixed it for you. Please test your patches
> in future.
Gah, apologies. Tested it in that other kernel tree I needed to
get this done for, then neglected to do so for cryptodev.
Thanks for the fixage.
--
Jarod Wilson
jarod@redhat.com
prev parent reply other threads:[~2009-05-06 12:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 1:18 [PATCH] crypto: don't raise alarm for no ctr(aes*) tests in fips mode Jarod Wilson
2009-04-29 10:50 ` Neil Horman
2009-04-29 12:46 ` Jarod Wilson
2009-04-30 21:13 ` [PATCH v2] crypto: don't raise alarm for no ctr(aes) tests Jarod Wilson
2009-05-01 11:54 ` Neil Horman
2009-05-04 11:10 ` [PATCH] crypto: don't raise alarm for no ctr(aes*) tests in fips mode Herbert Xu
2009-05-04 18:56 ` Jarod Wilson
2009-05-05 1:08 ` Herbert Xu
2009-05-05 3:45 ` Jarod Wilson
2009-05-05 5:29 ` Herbert Xu
2009-05-05 13:04 ` Jarod Wilson
2009-05-04 20:24 ` [PATCH] crypto: add ctr(aes) test vectors Jarod Wilson
2009-05-05 13:18 ` Herbert Xu
2009-05-05 13:55 ` Jarod Wilson
2009-05-05 14:42 ` [PATCH v2] " Jarod Wilson
2009-05-06 9:30 ` Herbert Xu
2009-05-06 12:51 ` Jarod Wilson [this message]
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=200905060851.34129.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.