[ODBC-228] Add parameter that corresponds to MARIADB_OPT_TLS_VERSION option from MariaDB Connector/C Created: 2019-03-06  Updated: 2019-04-04  Resolved: 2019-03-21

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: 3.1.0, 3.0.8
Fix Version/s: 3.0.9, 3.1.1

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Lawrin Novitsky
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to ODBC-238 Add parameter that corresponds to MYS... Closed
relates to ODBC-241 Add parameter that corresponds to MYS... Closed
relates to MDEV-14101 Provide option to select TLS protocol... Closed
relates to ODBC-239 Switch from deprecated mysql_options ... Closed
relates to ODBC-240 SSLFP and SSLFPLIST parameters appear... Closed
relates to ODBC-242 Add parameter that corresponds to MAR... Open

 Description   

MariaDB Connector/C 3.0 added the MARIADB_OPT_TLS_VERSION option with this commit:

https://github.com/MariaDB/mariadb-connector-c/commit/b241f8995fcd5dd6cfd0428e59171f47b7f757cc#diff-c61d6e7cbbec589fb76256c8af4a4159

It doesn't look like MariaDB Connector/ODBC supports that yet:

https://mariadb.com/kb/en/library/about-mariadb-connector-odbc/#tls-related-connection-parameters

Maybe it should add a TLSVERSION parameter that corresponds to MariaDB Connector/C's MARIADB_OPT_TLS_VERSION option?

 Comments   
Comment by Lawrin Novitsky [ 2019-03-21 ]

The patch has been pushed into odbc-3.0 as 172c399
Won't be merged into 2.0 as older C/C do not support this functionality

Connection string option name isTLSVERSION

This option can be used to enforce MARIADB_OPT_TLS_VERSION C/C option to
limit allowed for the connection TLS versions.
The value can be either a bitmap, where bit 1 corresponds to TLSv1.1,
bit 2 - TLSv1.2, and 4 - to TLSv1.3, or it can be set as combination of
string names TLSv1.1, TLSv1.2 and TLSv1.3.
Checkbox group has been added to the Windows setup dialog. If no
checkboxes checked there means all versions are allowed.

Generated at Thu Feb 08 03:27:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.