Skip to content

Commit a8b15f6

Browse files
author
Daniel Horecki
committed
Update ANNOUNCEMENT file
1 parent 57da949 commit a8b15f6

File tree

1 file changed

+66
-49
lines changed

1 file changed

+66
-49
lines changed

ANNOUNCEMENT

Lines changed: 66 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -35,65 +35,82 @@ Enjoy!
3535

3636
======================================================================
3737

38-
Changes in MySQL Connector/C++ 1.1.7
39-
40-
Configuration Notes
41-
42-
* Binary distributions for this release of MySQL
43-
Connector/C++ were linked against libmysqlclient from
44-
MySQL 5.7.10, except for OS X 10.8/10.9, for which
45-
distributions were linked against MySQL 5.7.9. This
46-
enables Connector/C++ to take advantage of features
47-
present in recent client library versions. Some examples:
48-
49-
+ Support for the MySQL JSON data type is available.
50-
Current versions of MySQL Workbench require JSON
51-
support, so to build MySQL Workbench 6.3.5 or higher
52-
from source, it is necessary to use a version of
53-
Connector/C++ at least as recent as 1.1.7.
54-
55-
+ Applications will attempt to establish a secure
56-
(encrypted) connection by default whenever the
57-
server is enabled to support secure connections, and
58-
fall back to an unencrypted connection otherwise.
59-
(This is as described at Configuring MySQL to Use
60-
Secure Connections
61-
(http://dev.mysql.com/doc/refman/5.7/en/using-secure
62-
-connections.html).) To enforce a secure connection,
63-
such that an error occurs if secure connections are
64-
not available, applications can enable the
65-
sslEnforce connection option.
66-
To build Connector/C++ from source, you must use either a
67-
General Availability version of MySQL 5.7 (5.7.9 or
68-
higher) or Connector/C 6.1.8 or higher. Set the MYSQL_DIR
69-
CMake option appropriately at configuration time as
70-
necessary. (Bug #22351273)
38+
Changes in MySQL Connector/C++ 1.1.8
7139

7240
Security Notes
7341

74-
* The linked OpenSSL library for Connector/C++ Commercial
75-
has been updated to version 1.0.1q. Issues fixed in the
76-
new OpenSSL version are described at
77-
http://www.openssl.org/news/vulnerabilities.html.
42+
* OpenSSL is ending support for version 1.0.1 in December
43+
2016; see
44+
https://www.openssl.org/policies/releasestrat.html.
45+
Consequently, Connector/C++ Commercial builds now use
46+
version 1.0.2 rather than version 1.0.1, and the linked
47+
OpenSSL library for the Connector/C++ Commercial has been
48+
updated from version 1.0.1 to version 1.0.2j. For a
49+
description of issues fixed in this version, see
50+
https://www.openssl.org/news/vulnerabilities.html.
7851
This change does not affect Oracle-produced MySQL
7952
Community builds of Connector/C++, which use the yaSSL
8053
library instead.
8154

82-
Spatial Data Support
83-
84-
* The required version of the Boost library for
85-
Connector/C++ builds has been raised to 1.56.0.
55+
Functionality Added or Changed
56+
57+
* Connector/C++ now supports a OPT_TLS_VERSION connection
58+
option for specifying the protocols permitted for
59+
encrypted connections. The option value is string
60+
containing a comma-separated list of one or more protocol
61+
names. Example:
62+
connection_properties["OPT_TLS_VERSION"] = sql::SQLString("TLSv1.1,TLS
63+
v1.2");
64+
65+
The permitted values depend on the SSL library used to
66+
compile MySQL: TLSv1, TLSv1.1, TLSv1.2 if OpenSSL was
67+
used; TLSv1 and TLSv1.1 if yaSSL was used. The default is
68+
to permit all available protocols.
69+
For more information about connection protocols in MySQL,
70+
see Secure Connection Protocols and Ciphers
71+
(http://dev.mysql.com/doc/refman/5.7/en/secure-connection
72+
-protocols-ciphers.html). (Bug #23496967)
73+
74+
* Connector/C++ now supports a OPT_SSL_MODE connection
75+
option for specifying the security state of the
76+
connection to the server. Permitted option values are
77+
SSL_MODE_PREFERRED (the default), SSL_MODE_DISABLED,
78+
SSL_MODE_REQUIRED, SSL_MODE_VERIFY_CA, and
79+
SSL_MODE_VERIFY_IDENTITY. These values correspond to the
80+
values of the --ssl-mode option supported by MySQL client
81+
programs; see Command Options for Secure Connections
82+
(http://dev.mysql.com/doc/refman/5.7/en/secure-connection
83+
-options.html). For example, this setting specifies that
84+
the connection should be unencrypted:
85+
connection_properties["OPT_SSL_MODE"] = sql::SSL_MODE_DISABLED;
86+
87+
The OPT_SSL_MODE option comprises the capabilities of the
88+
sslEnforce and sslVerify connection options.
89+
Consequently, both of those options are now deprecated.
90+
(Bug #23496952)
91+
92+
* Connector/C++ now supports OPT_MAX_ALLOWED_PACKET and
93+
OPT_NET_BUFFER_LENGTH connection options. Each option
94+
takes a numeric value. They correspond to the
95+
MYSQL_OPT_MAX_ALLOWED_PACKET and
96+
MYSQL_OPT_NET_BUFFER_LENGTH options for the
97+
mysql_options() C API function.
98+
99+
* Issues compiling Connector/C++ under Visual Studio 2015
100+
were corrected.
86101

87102
Bugs Fixed
88103

89-
* MySQL_Prepared_ResultSet::relative() failed to fetch the
90-
record due to a missing proxy->fetch() call. (Bug
91-
#21152054)
104+
* A segmentation fault could occur for attempts to insert a
105+
large string using a prepared statement. (Bug #23212333,
106+
Bug #81213)
107+
108+
* The certification verification checks that are enabled by
109+
the verifySSL connection option were not performed
110+
properly. (Bug #22931974)
92111

93-
* During Connector/C++ builds, the MySQL Server CXXFLAGS
94-
and CFLAGS values were used rather than the system
95-
default values. To specify explicitly to use the server
96-
values, enable the new USE_SERVER_CXXFLAGS CMake option.
97-
(Bug #77655, Bug #21391025)
112+
* Connector/C++ failed to compile against a version of the
113+
MySQL C API older than 5.7. (Bug #22838573, Bug #80539,
114+
Bug #25201287)
98115

99116
Enjoy!

0 commit comments

Comments
 (0)