Connection will fail if there is --ssl-mode=DISABLED under [xtrabackup]
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.4 |
Invalid
|
Medium
|
Unassigned |
Bug Description
Related to -> https:/
Based on -> https:/
We have concluded that, it pick the last one.
But for this scenario it differs:
[xtrabackup]
user=msandbox
password=msandbox
port = 5632
socket = /tmp/mysql_
ssl-mode=DISABLED
[client]
user=jeffrey
password=
port = 5632
socket = /tmp/mysql_
ssl-cert=
ssl-key=
ssl-ca=
The result:
$ ./xtrabackup --version
./xtrabackup version 2.4.5 based on MySQL server 5.7.13 Linux (x86_64) (revision id: fd5bd0f)
$ sudo ./xtrabackup --defaults-
[sudo] password for sh:
170117 15:14:32 Connecting to MySQL server host: localhost, user: jeffrey, password: set, port: 5632, socket: /tmp/mysql_
WARNING: no verification of server certificate will be done. Use --ssl-mode=
Failed to connect to MySQL server: Access denied for user 'jeffrey'
Result:
It will pick up user and pass from [client] but it will also be affected by --ssl-mode=DISABLED under [xtrabackup]
The same is not true for
$ ./xtrabackup --version
./xtrabackup version 2.3.6 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 21bdc87)
$ sudo ./xtrabackup --defaults-
[sudo] password for sh:
170117 15:14:38 Connecting to MySQL server host: localhost, user: jeffrey, password: set, port: 5632, socket: /tmp/mysql_
Using server version 5.6.32-debug
./xtrabackup version 2.3.6 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 21bdc87)
[client] section doesn't contain --ssl-mode, so it is taken from [xtrabackup]
Xtrabackup 2.4 handle ssl-mode and based on that is trying to connect without using SSL.
Xtrabackup 2.3 doesn't handle ssl-mode and thus is able to connect.
What is the bug here?