[ODBC-242] Add parameter that corresponds to MARIADB_OPT_TLS_CIPHER_STRENGTH option from MariaDB Connector/C Created: 2019-04-04  Updated: 2019-09-18

Status: Open
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: 3.1.0, 3.0.8
Fix Version/s: None

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

Issue Links:
Blocks
is blocked by CONC-439 Value of MARIADB_OPT_TLS_CIPHER_STREN... Open
Relates
relates to ODBC-228 Add parameter that corresponds to MAR... Closed
relates to ODBC-239 Switch from deprecated mysql_options ... Closed
relates to ODBC-240 SSLFP and SSLFPLIST parameters appear... Closed
relates to ODBC-241 Add parameter that corresponds to MYS... Closed
relates to ODBC-238 Add parameter that corresponds to MYS... Closed

 Description   

MariaDB Connector/C added the MARIADB_OPT_SSL_CIPHER_STRENGTH option in the following commit:

https://github.com/MariaDB/mariadb-connector-c/commit/509b948e7dda787d02f6c8fdd236060e4d38ad72

It looks like it was renamed to MARIADB_OPT_TLS_CIPHER_STRENGTH, probably in the following commit:

https://github.com/MariaDB/mariadb-connector-c/commit/4b1e94bccce482e979f1f337ba66d8c8a982ee84

https://github.com/MariaDB/mariadb-connector-c/blob/v3.0.9/include/mysql.h#L217

Should MariaDB Connector/ODBC add a parameter that corresponds to this option?



 Comments   
Comment by Lawrin Novitsky [ 2019-09-17 ]

I cannot see this option to be used any more. It's only use in set/get functions, and in the test.
Looks like it was "lost in merges". Maybe I am missing something, but so far there is no sense to add its support in C/ODBC.

Comment by Geoff Montee (Inactive) [ 2019-09-18 ]

I think you're right. I reported CONC-439 about that.

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