From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: James Hsiao <jhsiao@amcc.com>,
Shasi Pulijala <spulijala@amcc.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Bogus sha1 implementation in crypto4xx
Date: Tue, 14 Jul 2009 15:46:29 +0200 [thread overview]
Message-ID: <20090714134629.GI20288@secunet.com> (raw)
In-Reply-To: <20090714130600.GA11081@gondor.apana.org.au>
On Tue, Jul 14, 2009 at 09:06:00PM +0800, Herbert Xu wrote:
>
> This hasn't caused a problem before because we haven't started
> using ahash yet, apart from tcrypt which is single-threaded.
> I'm currently in the process of converting authenc (hence IPsec)
> across, which means that we will soon rely on the fact that
> you can have multiple hash operations ongoing at once.
>
As I pointed out already, I'm working on converting IPsec to ahash too.
So perhaps we can share the work to do not all the work twice.
I have ahash versions of authenc and ah4/ah6. The authenc ahash version
needs a hack in esp to be able to chain all scatterlist in authenc and I
wanted to look over it again before I post.
Today I finished with ah4/ah6. This needs still some tests but I could post
these two in the next days if you have not converted them it yet.
next prev parent reply other threads:[~2009-07-14 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 13:06 Bogus sha1 implementation in crypto4xx Herbert Xu
2009-07-14 13:46 ` Steffen Klassert [this message]
2009-07-14 14:43 ` Herbert Xu
2009-07-15 5:37 ` Steffen Klassert
2009-07-15 5:37 ` Herbert Xu
2009-07-29 22:58 ` Shasi Pulijala
2009-07-31 3:27 ` 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=20090714134629.GI20288@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=herbert@gondor.apana.org.au \
--cc=jhsiao@amcc.com \
--cc=linux-crypto@vger.kernel.org \
--cc=spulijala@amcc.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.