To quote book of all knowledge:
Starting with the MySQL Community 8.0.4-RC we are unifying on OpenSSL as the default TLS/SSL library for both MySQL Enterprise Edition and MySQL Community Edition. Previously, MySQL Community Edition used YaSSL.
Why make this change?
- Community Requests – Supporting OpenSSL in the MySQL Community Edition has been one of the most frequently requested features.
In the MySQL team, one of our focuses over the last few releases has been improving the usability of the MySQL Server for operations teams. The results can be seen in a number of areas:
- Our continued investment in Performance Schema.
Transport Layer Security (TLS, also often referred to as SSL) is an important component of a secure MySQL deployment, but the complexities of properly generating the necessary key material and configuring the server dissuaded many users from completing this task. MySQL Server 5.7 simplifies this task for both Enterprise and Community users. …
In November we held our first MySQL 5.8 planning session in London. On behalf of the MySQL team, I would like to thank you for your feature requests and suggestions. We reviewed over 150 pieces of feedback in total, and are looking forward to prioritizing a number of suggestions:
In MySQL 5.8, we are planning to make two important changes to modernize our code base.…
As Norvald wrote in his recent post:
A long time ago, libmysqlclient came in two versions: one that was thread safe and one that wasn’t. But that was a long time ago. Since MySQL 5.5, the thread safe libmysqlclient_r library has just been a symlink to the libmysqlclient library, which has been thread safe at least since then.