5 ms·
Just out of curiosity, why are you proposing that AES 128 is the one to go with? According to SSL Labs AES 256 is preferable and has broad support among browse
by samch 12y ago
Just out of curiosity, why are you proposing that AES 128 is the one to go with? According to SSL Labs AES 256 is preferable and has broad support among browsers.
- tuxychandru 12y agoThis article points to an attack that applies to AES-256, but not 128. https://www.schneier.com/blog/archives/2009/07/another_new_aes.html https://www.schneier.com/blog/archives/2009/07/another_new_a...
- samch 12y agoExcept that the attack you mention has no bearing on the standard 14-round AES-256 that everybody uses.
- davidben 12y agoAES_128_GCM is much much preferable to AES_256_CBC. AES_256_GCM does not have broad support (not supported by Chrome or Firefox) and isn't really worth the performance tradeoff. https://code.google.com/p/chromium/issues/detail?id=442572 https://code.google.com/p/chromium/issues/detail?id=442572
- count 12y agoSSL Labs is judging what they consider absolute security (I assume - I can't speak for Ivan or Qualys), where Google/Mozilla/etc look heavily at performance and supportability. Mozilla publishes their approach to what is 'best' here: https://wiki.mozilla.org/Security/Server_Side_TLS https://wiki.mozilla.org/Security/Server_Side_TLS