Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
3.0.8
-
None
-
None
Description
If we look at the mariadb_defaults[] array that's used to parse options from my.cnf or other option/configuration files, it looks like some TLS-related options are not settable in these files.
For example, here's the array in 3.0:
And here's the array in 3.1:
Some options that are not listed are:
- MYSQL_OPT_SSL_CRL
- MYSQL_OPT_SSL_CRLPATH
- MYSQL_OPT_SSL_ENFORCE
- MARIADB_OPT_TLS_CIPHER_STRENGTH
- MARIADB_OPT_TLS_PEER_FP
- MARIADB_OPT_TLS_PEER_FP_LIST
Does it make sense to add some or all of these to the mariadb_defaults[] array?
Attachments
Issue Links
- blocks
-
MDEV-19035 Make MariaDB Connector/C handle my.cnf parsing for clients
- Open
- relates to
-
CONC-327 !include/!includedir not parsed in my.cnf
- Closed
-
CONC-395 Dashes and underscores are not interchangeable in options in my.cnf
- Closed
-
CONC-396 !includedir in my.cnf does not include all .cnf and .ini files in the directory
- Open
-
CONC-402 Replace underscores with dashes in conf_key values in mariadb_defaults array
- Closed
-
ODBC-229 Add parameters that correspond to MYSQL_READ_DEFAULT_FILE and MYSQL_READ_DEFAULT_GROUP options from MariaDB Connector/C
- Closed
-
CONC-415 Option prefixes not supported in my.cnf
- Open
-
CONC-416 On Windows, C/C looks for first my.cnf/my.ini in GetSystemDirectory() instead of GetSystemWindowsDirectory()
- Closed