I tested mageia.org on ssllabs.com. I got the following result https://www.ssllabs.com/ssltest/analyze.html?d=mageia.org&s=217.70.188.116 In summary, it says * This server does not mitigate the CRIME attack. Grade capped to B. * Experimental: This server is vulnerable to the OpenSSL CCS vulnerability (CVE-2014-0224), but probably not exploitable. * The server supports only older protocols, but not the current best TLS 1.2. Grade capped to B. * The server does not support Forward Secrecy with the reference browsers. MORE INFO » * This server is not vulnerable to the Heartbleed attack. Could you update the server to take into account thiese remarks? Reproducible: Steps to Reproduce:
Summary: SSL support needs to be improvec => SSL support needs to be improved
Assignee: atelier-bugs => sysadmin-bugsQA Contact: (none) => atelier-bugs
A new test gives now * This server is vulnerable to the POODLE attack. If possible, disable SSL 3 to mitigate. Grade capped to C. MORE INFO » * This server does not mitigate the CRIME attack. Grade capped to B. * Certificate uses SHA1 and expires after 2016. Upgrade to SHA256 as soon as possible to avoid browser warnings. MORE INFO » * The server supports only older protocols, but not the current best TLS 1.2. Grade capped to B. * The server does not support Forward Secrecy with the reference browsers. MORE INFO » In these conditions, I think it is really dangerous to keep the https version of mageia.org: users think their communication with mageia.org are protected which is not really the case...
Ping?
CC: (none) => doktor5000
Few months after, it gives * This server is vulnerable to the POODLE attack. If possible, disable SSL 3 to mitigate. Grade capped to C. MORE INFO » Certificate has a weak signature and expires after 2016. Upgrade to SHA2 to avoid browser warnings. MORE INFO » * This server accepts the RC4 cipher, which is weak. Grade capped to B. MORE INFO » * The server does not support Forward Secrecy with the reference browsers. MORE INFO » * This site works only in browsers with SNI support. * This server supports TLS_FALLBACK_SCSV to prevent protocol downgrade attacks. Briefly, it is a bit better, but there is still this POODLE attack vulnerability...
*** Bug 16013 has been marked as a duplicate of this bug. ***
CC: (none) => bjarne.thomsen
For apache, using these settings would help : SSLVerifyClient none SSLProtocol +TLSv1.2 +TLSv1.1 +TLSv1 SSLHonorCipherOrder on SSLCipherSuite ALL:!aNULL:!eNULL:!LOW:!EXP:!RC4:!3DES:+HIGH:+MEDIUM and also : Header add Strict-Transport-Security "max-age=15768000;includeSubDomains"
CC: (none) => makowski.mageia
According to ssllabs site Overall Rating is now declared as A.
Status: NEW => RESOLVEDCC: (none) => filip.komarResolution: (none) => FIXED