From: Jarod Wilson <jarod@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Herbert Xu <herbert.xu@redhat.com>
Subject: Re: [PATCH] add self-tests for rfc4309(ccm(aes))
Date: Mon, 13 Apr 2009 17:03:48 -0400 [thread overview]
Message-ID: <200904131703.50196.jarod@redhat.com> (raw)
In-Reply-To: <20090410023108.GA7933@localhost.localdomain>
On Thursday 09 April 2009 22:31:08 Neil Horman wrote:
> On Thu, Apr 09, 2009 at 03:16:53PM -0400, Jarod Wilson wrote:
> > On Thursday 09 April 2009 14:52:04 Neil Horman wrote:
> > > On Thu, Apr 09, 2009 at 02:34:59PM -0400, Jarod Wilson wrote:
> > > > Patch is against current cryptodev-2.6 tree, successfully tested via
> > > > 'modprobe tcrypt type=45'. The number of test vectors might be a bit
> > > > excessive, but I tried to hit a wide range of combinations of varying
> > > > key sizes, associate data lengths, input lengths and pass/fail.
> > > >
> > > > Signed-off-by: Jarod Wilson <jarod@redhat.com>
Ugh. I clearly missed *something* when testing, there's no way the patch
I sent actually fully passed. I have things working for real now though
locally, including a back-port to a certain 2.6.18-based kernel. :)
Updated patch or patches forthcoming... (probably tomorrow)
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2009-04-13 21:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 18:34 [PATCH] add self-tests for rfc4309(ccm(aes)) Jarod Wilson
2009-04-09 18:52 ` Neil Horman
2009-04-09 19:16 ` Jarod Wilson
2009-04-10 2:31 ` Neil Horman
2009-04-13 21:03 ` Jarod Wilson [this message]
2009-04-13 23:11 ` [PATCH v2] crypto: " Jarod Wilson
2009-04-14 11:13 ` Neil Horman
2009-04-15 11:20 ` Herbert Xu
2009-04-15 12:35 ` Jarod Wilson
2009-04-15 13:35 ` [PATCH 0/3] crypto: add testmgr support and self-tests for rfc4309 Jarod Wilson
2009-04-15 13:36 ` [PATCH 1/3] crypto: properly handle null input and assoc data aead test vectors Jarod Wilson
2009-04-20 6:23 ` Herbert Xu
2009-04-23 17:30 ` Jarod Wilson
2009-04-15 13:36 ` [PATCH 2/3] crypto: handle ccm dec test vectors expected to fail verification Jarod Wilson
2009-04-20 6:25 ` Herbert Xu
2009-04-23 17:31 ` Jarod Wilson
2009-04-15 13:37 ` [PATCH 3/3] crypto: add self-tests for rfc4309(ccm(aes)) Jarod Wilson
2009-04-20 6:26 ` Herbert Xu
2009-04-23 18:17 ` [PATCH v4 0/2] crypto: add testmgr support and self-tests for rfc4309 Jarod Wilson
2009-04-23 18:22 ` [PATCH 1/2] crypto: handle ccm dec test vectors expected to fail verification Jarod Wilson
2009-04-23 18:23 ` [PATCH 2/2] crypto: add self-tests for rfc4309(ccm(aes)) Jarod Wilson
2009-05-04 11:24 ` [PATCH v4 0/2] crypto: add testmgr support and self-tests for rfc4309 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=200904131703.50196.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=herbert.xu@redhat.com \
--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 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).