[MDEV-31934] CHANGE MASTER does not pick up TLS defaults from config file as documented Created: 2023-08-16 Updated: 2023-11-23 Resolved: 2023-09-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Documentation, Replication, SSL |
| Affects Version/s: | 10.6.15, 11.1.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Hartmut Holzgraefe | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
According to https://mariadb.com/kb/en/replication-with-secure-connections/#setting-tls-client-options-in-an-option-file TLS certificate options like MASTER_SSL_CA, MASTER_SSL_CERT and MASTER_SSL_KEY can either be set explicitly in a CHANGE MASTER command, or will be fetched from respective options in the [client] or [client-mariadb] section of the config file(s). I could not get this to work (tried with 10.6 and 11.1 so far), and looking at the server code I don't see yet how it could possibly use any client section settings either. I verified that the client options are set correctly by setting up:
and creating a replication user requiring to-way/mutual TLS using:
I verified that from the slave host I can connect to the master using that user, and that it fails when not reading the option file(s), due to the client no longer offering a client certificate for two-way TLS:
Same problem when setting up the slave with just
When explicitly adding
the slave can start just fine. I also verified with WireShark that in the failed case no client certificate was offered to the server during TLS handshake. |
| Comments |
| Comment by Hartmut Holzgraefe [ 2023-09-04 ] |
|
Why is this closed now? |
| Comment by Sergei Golubchik [ 2023-09-04 ] |
|
because the mismatch between the documentation and the implementation is fixed, the documentation no longer claims that the server reads client sections of my.cnf |