RE: [PATCH 2/2] Crypto: Add support for 192 & 256 bit keys to AESNI RFC4106 - fixed whitespace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks.  
I'll get the revision for glue.c done ( and the e-mail problem fixed, probably from a different address) soon.  

	- Tim

-----Original Message-----
From: Tim Chen [mailto:tim.c.chen@xxxxxxxxxxxxxxx] 
Sent: Monday, March 10, 2014 7:11 PM
To: McCaffrey, Timothy M
Cc: herbert@xxxxxxxxxxxxxxxxxxx; linux-crypto@xxxxxxxxxxxxxxx; James Guilford; Vinodh Gopal
Subject: RE: [PATCH 2/2] Crypto: Add support for 192 & 256 bit keys to AESNI RFC4106 - fixed whitespace

On Fri, 2014-03-07 at 19:56 -0600, McCaffrey, Timothy M wrote:
> Ok, will generate another patch for glue.c.  Since the asm doesn't verify the aadlen or taglen either (they have a constrained set of values as well), perhaps they should be verified by glue.c as well?
> 
> 	- Tim
> 

Ran through the validation tests and the new code looks good.  The
performance difference is negligible between the new and original 
code for 128 bit key.

Tim Chen

��.n��������+%������w��{.n�����{���{ay�ʇڙ���f���h������_�(�階�ݢj"��������G����?���&��





[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux