Jump to: navigation, search

Security/Server Side TLS

1 byte removed, 13:01, 29 October 2016
followed but --> followed by - hopefully corrected what appeared to be an English misuse or typo (I may still need to get this change into github)
* ChaCha20 is prefered as the fastest and safest in-software cipher, followed but by AES128. Unlike the modern configuration, we do not assume clients support AESNI and thus do not prioritize AES256 above 128 and ChaCha20. There has been discussions ([ 1], [ 2]) on whether AES256 extra security was worth its computing cost in software (without AESNI), and the results are far from obvious. At the moment, AES128 is preferred, because it provides good security, is really fast, and seems to be more resistant to timing attacks.
* DES-CBC3-SHA and EDH-RSA-DES-CBC3-SHA are maintained for backward compatibility with clients that do not support AES.
* While the goal is to support a broad range of clients, we reasonably disable a number of ciphers that have little support (such as SEED, CAMELLIA, ...).

Navigation menu