com.sun.crypto.provider.GHASH performance fix

Anthony Scarpino anthony.scarpino at oracle.com
Fri Jan 16 08:18:35 UTC 2015


> On Jan 15, 2015, at 12:26 PM, Florian Weimer <fweimer at redhat.com> wrote:
> 
> Yes, they are going to help quite a bit as well.  The other thing we need to fix for TLS is that AES-GCM is a garbage collector stress test.  Last time I looked, for each transferred byte, there were four bytes allocated on the heap.

What exactly are you referring to here?  Is there a problem in TLS where it is using too much memory for AES-GCM specifically or AES-GCM itself is using too much memory?  What test did you do to see this heap allocation or is this code inspection?

thanks

Tony



More information about the security-dev mailing list