Upgrade libmysqlclient.a for TLSv1.1 support (for MariaDB 10.4 default installs) #3492
Sequel Pro currently appears to ship a
The most recent GA release of MariaDB, version 10.4.6, replaces the embedded yaSSL library (not maintained) with wolfSSL (maintained, supports modern TLS) and ships with a newly introduced
Would it be possible to upgrade the MySQL client library to a newer release to make it support a slightly more modern version of TLS? That would allow Sequel Pro to connect to MariaDB 10.4 servers out of the box and also improve security.
"wolfSSL" is AFAIK just a rebranding of yaSSL.
SP is mostly stuck with 5.5 because IIRC 5.6 introduced breaking changes in how some functions in the client libraries behave, thus someone would have to step through the source code or the changelogs and compare those in detail, which is quite a bit of effort.
Personally I think it would be better to get rid of the SSL library dependency altogether and use the Apple provided library (SecureTransport or CF Networking), like all native OS X apps would, but that also is a lot of effort.
Thanks for the feedback.
Right, it seems they renamed CyaSSL to wolfSSL in 2015. CyaSSL was their C port/product of their C++ yaSSL SSL library.
Any idea what these functions in the client libraries would be? I did
In the process I found a build script for building
FWIW, I ended up with something that allowed me connect to MariaDB 10.4.6 (requires TLSv1.1) and a few AWS RDS MySQL 5.6 and Aurora MySQL servers (still using TLSv1.0).