Hi,
after upgrading from 6.0.44 to 7.0.12-a without changing anything, I ran a ssl-security-test on
https://www.ssllabs.com/ssltest/against our ssl-sites.
It complained heavily about the following ciphers, which are very weak because they just use DH with 512 Bits!
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x6b) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x16) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x67) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x45) DH 512 bits (p: 64, g: 1, Ys: 64) WEAK
After disabling those ciphers it got even worse, because then all the anonymous DH ciphers are being used, which should be disabled
by default because they can lead to a MITM attack.
I like the new feature that I can decide on my own which ciphers to enable, but I don't understand why these weak ciphers
are enabled by default. This may expose a lot of customers to a security risk without them knowing it.
Best Regards
Tim