MySQL :: MySQL Connector/C++ Release Notes :: Changes in MySQL Connector/C++ 8.0.28 (2022-01-18, General Availability)

MySQL Connector/C++ Release Notes / Changes in MySQL Connector/C++ 8 / Changes in MySQL Connector/C++ 8.0.28 (2022-01-18, General Availability)

The TLSv1 and TLSv1.1 connection protocols were deprecated in Connector/C++ 8.0.26 and now are removed in this release. The removed values are considered invalid for use with connection options and session settings. Connections can be made using the more-secure TLSv1.2 and TLSv1.3 protocols. TLSv1.3 requires that both the server and Connector/C++ be compiled with OpenSSL 1.1.1 or higher. (WL #14816, WL #14818)

Applications that use the legacy JDBC API now can establish connections using multifactor authentication, such that up to three passwords can be specified at connect time. The new OPT_PASSWORD1, OPT_PASSWORD2, and OPT_PASSWORD3 connection options are available for specifying the first, second, and third multifactor authentication passwords, respectively. OPT_PASSWORD1 is an alias for the existing OPT_PASSWORD option; if both are given, OPT_PASSWORD is ignored. (WL #14658)

For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for Connector/C++ has been updated to version 1.1.1l. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html. (Bug #33309902)

For connections made using X Protocol, getting BIT(1) column data by calling getRawBytes() returned an empty buffer. BIT is treated as an unsigned integer (uint64_t), which means applications can get or set the value by using such a type. (Bug #33335148)

PREV HOME UP NEXT