Bad SSLLabs report for dolphin-emu.org

[seredlek]

Hello i routinely scan all https:// pages that i encounter with ssllabs ssl test, and the results for the domain dolphin-emu.org look really shocking.
https://www.ssllabs.com/ssltest/analyze.html?d=dolphin-emu.org

This page uses a lot of weak and insecure ciphers:

Quote: Cipher Suites (sorted by strength; the server has no preference)

[color=red]SSL_CK_RC4_128_EXPORT40_WITH_MD5 (0x20080) INSECURE 40[/color]
[color=red]SSL_CK_RC2_128_CBC_EXPORT40_WITH_MD5 (0x40080) INSECURE[/color] [color=red]40[/color]
[color=red]SSL_CK_DES_64_CBC_WITH_MD5 (0x60040) INSECURE[/color] [color=red]56[/color]
[color=#F88017]TLS_RSA_WITH_DES_CBC_SHA (0x9) WEAK[/color] [color=#F88017]56[/color]
[color=red]SSL_CK_RC4_128_WITH_MD5 (0x10080) INSECURE[/color] [color=red]128[/color]
[color=red]SSL_CK_RC2_128_CBC_WITH_MD5 (0x30080) INSECURE[/color] [color=red]128[/color]
TLS_RSA_WITH_RC4_128_MD5 (0x4) 128
TLS_RSA_WITH_RC4_128_SHA (0x5) 128
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) 128
[color=red]SSL_CK_DES_192_EDE3_CBC_WITH_MD5 (0x700c0) INSECURE[/color] [color=red]168[/color]
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) 168
TLS_RSA_WITH_AES_256_CBC_SHA (0x35) 256

Instead of TLS 1.2 or 1.1 we have the insecure and redundant SSL2

Quote: Protocols
TLS 1.2 No
TLS 1.1 No
TLS 1.0 Yes
SSL 3 Yes
[color=red]SSL 2 INSECURE[/color][color=red] Yes[/color]

and finally some flaws that allow ddos attacks:

Quote: Protocol Details
[color=green]Secure Renegotiation[/color]
[color=green]Supported[/color]

[color=#F88017]Secure Client-Initiated Renegotiation[/color]
[color=#F88017]Supported DoS DANGER
[/color]
Insecure Client-Initated Renegotiation
No

[color=#F88017]BEAST attack[/color]
[color=#F88017]Not mitigated server-side[/color]
SSL 3: 0x9, TLS 1.0: 0x9

[color=red]TLS compression[/color]
[color=red]Yes INSECURE ([color=red]more info[/color])[/color]

RC4
Yes, but not used by modern browsers

[color=#F88017]Forward Secrecy[/color]
[color=#F88017]No NOT DESIRABLE ([color=#F88017]more info[/color])[/color]

Next Protocol Negotiation
No

[color=red]Session resumption[/color]
[color=red]No (IDs assigned but not accepted)[/color]

I think all these quoted things make using ssl redundant on this page and should be dealt with asap.

[delroth]

Feel free to strip the SSL on your side if you think it's redundant.

[seredlek]

Maybe redundant is the wrong word.
The reason for this topic was to highlight the problem and hopefully see a more secure configuration as a result of it.
https://www.ssllabs.com/downloads/SSL_TLS_Deployment_Best_Practices_1.3.pdf might help

[Oehr]

as the mod closed the old thread instead of merging, here is the post again to continue the discussion:

SSL 3.0, RC4, DES, 3DES, MD5 and SHA-1 - Old and busted encryption

https://www.ssllabs.com/ssltest/analyze.html?d=dolphin-emu.org

Obsolete SSL 3.0, without TLS as an alternative, along with the recent announcement of the POODLE attack, the website really needs a HTTPS upgrade:

Please disable SSL 3.0 entirely (to block downgrading from TLS) and add TLS 1.0 through 1.2 instead.

As for ciphers: All ciphers using RC4, DES, 3DES or MD5 (or a combination of those) are also considered broken and obsolete, so I suggest using only secure ciphers (that may also support perfect forward secrecy) whenever possible!

The certificate also needs an upgrade, as its still signed with SHA-1, which is also considered broken. Please do not just sign it again: Generate a new and longer key and sign that with SHA-2 (or SHA-3)

Additional reasons as to why this should be done real soon, aside from the obvious and dangerous security flaw:
1. Recent news (POODLE attack) have made this a much more pressing issue (its basically SSL 3.0's final nail in its coffin)
2. The situation from back when this thread was opened worsened: TLS 1.0 is NOT supported anymore for whatever reason. Only the highly insecure and flawed SSL 3.0 is.*
3. Browsers will probably drop SSL3 support soon or at least be shipped with it disabled.

[Oehr]

Seems like the admin(s) already responded: dolphin-emu.org is TLSv1.0 only now!

I hope to see them step towards the future as well, with proper cipher suits and support for TLSv1.2. For that, you need to upgrade from openssl 0.9.8 though. as you are still stuck on that old version, I suspect youre still running debian 6 with apache2.2 as well. neither are up to date.

Here is my compilation of apache settings that will improve security without you updating any software. still: update is highly recommended!
SSLCompression off
SSLHonorCipherOrder on
SSLCipherSuite ALL:-EXP:-RC4:-RC2:-DES:-3DES:-MD5:-NULL
SSLProtocol ALL -SSLv3 -SSLv2


TLS compression is bad. PLEASE DEACTIVATE IT. Security flaw! https://en.wikipedia.org/wiki/CRIME