3 ms·
>It pointlessly excludes clients since TLS 1.0, 1.1 and AES >128 are still considered secure. Wrong. All AES-based ciphers in TLS 1.0/1.1 are vulnerable to th
by hannob 10y ago
>It pointlessly excludes clients since TLS 1.0, 1.1 and AES
>128 are still considered secure.
Wrong.
All AES-based ciphers in TLS 1.0/1.1 are vulnerable to the Lucky Thirteen attack. This can be avoided by careful implementation, however as far as I know the go developers don't even try to do that and say if you want something secure use gcm.
- rgbrenner 10y agoWrong. 1. TLS 1.2 is also vulnerable to the lucky thirteen attack. 2. The lucky thirteen attack requires CBC-mode.. which is also what generates the obsolete crypto warning in chrome. The solution here is clearly to disable CBC-mode. http://www.isg.rhul.ac.uk/tls/TLStiming.pdf http://www.isg.rhul.ac.uk/tls/TLStiming.pdf