On Wed, Jul 15, 2009 at 07:37:33AM +0200, Steffen Klassert wrote:
>
> Ok, for a moment I thought we both working at the same thing :)
> I'll finalize my work and send everything in the next days.
I'm pretty much done with the ahash rework so whenever you're
ready please send the authenc conversion
On Tue, Jul 14, 2009 at 10:43:44PM +0800, Herbert Xu wrote:
>
> Sure, go ahead. I'm still redoing the ahash infrastructure to
> properly support finup and export/import.
>
Ok, for a moment I thought we both working at the same thing :)
I'll finalize my work and send everything in the next days.
On Tue, Jul 14, 2009 at 10:26:15PM +0200, Sebastian Andrzej Siewior wrote:
>
> I have here a via nano so I should be able to test it.
> Do you have a particular test case in mind or should I just grab
> ipsec-tools, setup a tunnel and send a few packets?
Yes, that should be enough. You don't eve
* Herbert Xu | 2009-07-11 18:19:58 [+0800]:
>As I don't have the hardware supporting padlock-sha, could someone
>with access to it please test this for me? In particular, I'd like
>to see this tested with an actual IPsec connection.
I have here a via nano so I should be able to test it.
Do you ha
On Tue, Jul 14, 2009 at 03:46:29PM +0200, Steffen Klassert wrote:
>
> 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
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 r
Hi:
I just noticed that the sha1 implementation in crypto4xx is
fundamentally broken. It stores the hash state in the context
of the tfm, instead of the context of the request.
This means that at any one time you can only have one entity
using the tfm, which is infeasible for an asynchronous has