Bug #75239 Support for TLSv1.1 and TLSv1.2
Submitted: 16 Dec 2014 21:08 Modified: 17 Mar 2016 13:56
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Security: Encryption Severity:S4 (Feature request)
Version:5.6.22, 5.7.8 OS:Any
Assigned to: CPU Architecture:Any
Tags: SSL, tls

[16 Dec 2014 21:08] Daniël van Eeden
The server only supports TLSv1.0.

Support for SSLv2 and SSLv3 should not be enabled as those protocols are broken. However support for TLSv1.1 and TLSv1.2 would be nice.

How to repeat:
5.6.22 with YaSSL:

mysql> SHOW GLOBAL STATUS LIKE 'Ssl_version';
| Variable_name | Value |
| Ssl_version   | TLSv1 |
1 row in set (0.01 sec)

Suggested fix:
Add support for newer SSL/TLS protocols.
[16 Dec 2014 21:28] Daniël van Eeden
Patch: not fully tested, but the basics work when using WITH_SSL=system

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: 0001-Add-support-for-TLSv1.1-and-TLSv1.2.patch (text/x-diff), 1.79 KiB.

[16 Dec 2014 21:30] Daniël van Eeden
It looks like Ssl_cipher_list gets truncated.

mysql> SHOW GLOBAL STATUS LIKE 'Ssl_version'\G
*************************** 1. row ***************************
Variable_name: Ssl_version
        Value: TLSv1.2
1 row in set (0.00 sec)

mysql> SHOW GLOBAL STATUS LIKE 'Ssl_cipher_list'\G
*************************** 1. row ***************************
Variable_name: Ssl_cipher_list
1 row in set (0.00 sec)
[16 Dec 2014 21:34] Daniël van Eeden
Eventually it might be nice to have a variable to enable/disable TLSv1.0 and TLSv1.1
[17 Dec 2014 7:38] MySQL Verification Team
Hello Daniël,

Thank you for the feature request and contribution.

[25 Dec 2014 13:53] Daniël van Eeden
It looks like this bug also limits programs which libmysqlclient (e.g. Workbench) to only use TLSv1.0
[23 Jun 2015 16:00] Michał Staruch
May I ask what are you waiting for, dear MySQL team? TLSv1.0 is already scheduled to be banned by PCI DSS v3.1: https://www.pcisecuritystandards.org/documents/Migrating_from_SSL_Early_TLS_Information%20... - so how about moving forward and adding support for 9-years old TLSv1.1 (RFC 4346) and 7-years old TLSv1.2 (RFC 5246)?

Just don't forget about ECC (RFC 4492), and stuff like ECDH curve selection (some people may prefer P-521). Also option for picking DH param would be needed (some of us want 4096).
[20 Aug 2015 21:39] Kevin Wilson
Can we please get an update on when TLS 1.2 will be supported for MySQL?
[30 Aug 2015 10:04] Daniël van Eeden
This patch fully works with MySQL compiled with OpenSSL (tested with 5.7.8)

With MySQL compiled with YaSSL the server uses TLSv1.0, but the client can connect to a server with OpenSSL and use TLSv1.1.

Note that YaSSL doesn't support TLSv1.2 yet

WolfSSL (formerly CYaSSL) does support TLSv1.2 (and CRL, etc)

The patch against 5.7.8:
[7 Dec 2015 11:21] Laurynas Biveinis

"Previously, MySQL supported only the TLSv1 protocol for encrypting secure connections. TLS support has been extended to enable a higher level of encrypted connection security:

When compiled using OpenSSL 1.0.1 or higher, MySQL supports the TLSv1, TLSv1.1, and TLSv1.2 protocols.

When compiled using the bundled version of yaSSL, MySQL supports the TLSv1 and TLSv1.1 protocols."
[17 Mar 2016 13:56] Daniël van Eeden
I consider this fixed