Now Google Chrome more faster on Android.
New TLS cipher suite in Chrome that operates three times faster than AES-GCM on devices that don't have AES hardware acceleration, including most Android phones, wearable devices such as Google Glass and older computers.
This improves user experience, reducing latency and saving battery life by cutting down the amount of time spent encrypting and decrypting data.
The benefits of this new cipher suite include:
Better security:-
ChaCha20 is immune to padding-oracle attacks, such as the Lucky13, which affect CBC mode as used in TLS. By design, ChaCha20 is also immune to timing attacks. Check out a detailed description of TLS ciphersuites weaknesses in our earlier post.
Better performance:-
ChaCha20 and Poly1305 are very fast on mobile and wearable devices, as their designs are able to leverage common CPU instructions, including ARM vector instructions. Poly1305 also saves network bandwidth, since its output is only 16 bytes compared to HMAC-SHA1, which is 20 bytes. This represents a 16% reduction of the TLS network overhead incurred when using older ciphersuites such as RC4-SHA or AES-SHA.
The expected acceleration compared to AES-GCM for various platforms is summarized in the chart below.
See more Details here :
http://googleonlinesecurity.blogspot.in/2014/04/speeding-up-and-strengthening-https.html
This improves user experience, reducing latency and saving battery life by cutting down the amount of time spent encrypting and decrypting data.
The benefits of this new cipher suite include:
Better security:-
ChaCha20 is immune to padding-oracle attacks, such as the Lucky13, which affect CBC mode as used in TLS. By design, ChaCha20 is also immune to timing attacks. Check out a detailed description of TLS ciphersuites weaknesses in our earlier post.
Better performance:-
ChaCha20 and Poly1305 are very fast on mobile and wearable devices, as their designs are able to leverage common CPU instructions, including ARM vector instructions. Poly1305 also saves network bandwidth, since its output is only 16 bytes compared to HMAC-SHA1, which is 20 bytes. This represents a 16% reduction of the TLS network overhead incurred when using older ciphersuites such as RC4-SHA or AES-SHA.
The expected acceleration compared to AES-GCM for various platforms is summarized in the chart below.
See more Details here :
http://googleonlinesecurity.blogspot.in/2014/04/speeding-up-and-strengthening-https.html
Comments
Post a Comment