Re: 256-bits cipher for HTTP/2 with Chrome

2016-01-15 Thread Reindl Harald



Am 15.01.2016 um 12:00 schrieb Jan Ehrhardt:

No question or issue, just a quick note.

On Apachelounge Mario Brandt (aka James Bond) once asked the question:
"Is there any chance to have a 256 cipher instead of
ECDHE-RSA-AES128-GCM-SHA256?"

It turns out, that there is a 256-bits cipher which will be used by Chrome
for HTTP/2 connections: ECDHE-RSA-CHACHA20-POLY1305

Further reading: https://www.apachelounge.com/viewtopic.php?p=32641#32641


given that AES is hardware accelerated (on client and server) these days 
and there is no compelling reason to prefer 256 bit because you would 
need a RSA-16000 (at least for AES256, not sure for CHACHA) while for 
AES128 RSA-3072 key.




signature.asc
Description: OpenPGP digital signature


256-bits cipher for HTTP/2 with Chrome

2016-01-15 Thread Jan Ehrhardt
No question or issue, just a quick note.

On Apachelounge Mario Brandt (aka James Bond) once asked the question:
"Is there any chance to have a 256 cipher instead of
ECDHE-RSA-AES128-GCM-SHA256?"

It turns out, that there is a 256-bits cipher which will be used by Chrome
for HTTP/2 connections: ECDHE-RSA-CHACHA20-POLY1305

Further reading: https://www.apachelounge.com/viewtopic.php?p=32641#32641
--
Jan