MySQL Forums :: Announcements :: MySQL Connector/ODBC 5.3.7 has been released


Advanced Search

MySQL Connector/ODBC 5.3.7 has been released
Posted by: Sreedhar S ()
Date: December 13, 2016 05:01AM

Dear MySQL users,

MySQL Connector/ODBC 5.3.7, a new version of the ODBC driver for
the MySQL database management system, has been released.

The available downloads include both a Unicode driver and an ANSI
driver based on the same modern codebase. Please select the driver type
you need based on the type of your application - Unicode or ANSI.
Server-side prepared statements are enabled by default. It is suitable
for use with any MySQL version from 5.5.

This is the fourth release of the MySQL ODBC driver conforming to the
ODBC 3.8 specification. It contains implementations of key 3.8 features,
including self-identification as a ODBC 3.8 driver, streaming of output
parameters (supported for binary types only), and support of the
SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver
only).

Also, Connector/ODBC 5.3 introduces a GTK+-based setup library
providing a GUI DSN setup dialog on some Unix-based systems, currently
included in the Debian 7/8, EL6/OL6, EL7/OL7 (64-bit only), Fedora 24/25,
FreeBSD 10/11, SLES 12, Ubuntu 12/14/16 packages. Other new
features in the 5.3 driver are FileDSN and Bookmarks support.

The release is now available in source and binary form for a number of
platforms from our download pages at

   http://dev.mysql.com/downloads/connector/odbc/5.3.html

For information on installing, please see the documentation at

http://dev.mysql.com/doc/connector-odbc/en/connector-odbc
-installation.html

Enjoy!

The MySQL Connectors team at Oracle

Changes in MySQL Connector/ODBC 5.3.7      (2016-12-13)

   Security Notes

     * Security Fix: The linked OpenSSL library for
       Connector/ODBC Commercial 5.3.7 has been updated from
       version 1.0.1q to version 1.0.2j. Versions of OpenSSL
       prior to 1.0.2j are reported to be vulnerable to
       CVE-2016-6304
       (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-20
        16-6304).
       This change does not affect the Oracle-produced MySQL
       Community build of Connector/ODBC 5.3.7, which uses the
       yaSSL library instead. (Bug #24753385, CVE-2016-6304)

   Functionality Added or Changed

     * A new configuration option, SSL_MODE, has been introduced
       for setting the SSL mode of the connection to the server.
       This option overrides the now deprecated sslverify and
       SSL_ENFORCE options. See Connector/ODBC DSN Configuration
       Options
       (http://dev.mysql.com/doc/connector-odbc/en/connector-o
        dbc-configuration-connection-parameters.html#codbc-dsn-co
        nfig-options) for details. (Bug #23497043)

     * Added new configuration option NO_TLS_1_0, NO_TLS_1_1,
       and NO_TLS_1_2 for controlling TLS versions for
       encrypting connecting. See Connector/ODBC DSN
       Configuration Options
       (http://dev.mysql.com/doc/connector-odbc/en/connector-o
        dbc-configuration-connection-parameters.html#codbc-dsn-co
        nfig-options) for details. For more information about
       connection protocols in MySQL, see Secure Connection
       Protocols and Ciphers
       (http://dev.mysql.com/doc/refman/5.7/en/secure-connection
        -protocols-ciphers.html).
       (Bug #23496903)

   Bugs Fixed

     * An assertion failure occurred when mysql_stmt_close()
       (http://dev.mysql.com/doc/refman/5.7/en/mysql-stmt-close.
        html) was called on a broken connection. (Bug #25109356)

     * Connector/ODBC could not be built with CMake 3.0.2 or
       later. The build script has been fixed to correct the
       issue. (Bug #22746557)

On behalf on the MySQL RE Team.
-Sreedhar S 


Options: ReplyQuote


Subject Views Written By Posted
MySQL Connector/ODBC 5.3.7 has been released 2474 Sreedhar S 12/13/2016 05:01AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.