[MDEV-28428] Master_SSL_Crl shows Master_SSL_CA value in SHOW SLAVE STATUS output Created: 2022-04-27  Updated: 2022-04-28  Resolved: 2022-04-28

Status: Closed
Project: MariaDB Server
Component/s: Admin statements, Replication
Affects Version/s: 10.3.34, 10.4.24, 10.5.15, 10.6.7, 10.7.3, 10.8.2
Fix Version/s: 10.2.44, 10.3.35, 10.4.25, 10.5.16, 10.6.8, 10.7.4

Type: Bug Priority: Major
Reporter: Hartmut Holzgraefe Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None


 Description   

When running SHOW SLAVE STATUS on a slave set up to use SSL/TLS encryption to fetch binlog events from the master the Master_SSL_Crl field in the status output wrongly shows the same value as Master_SSL_CA.

E.g. set up slave with:

CHANGE MASTER TO 
   MASTER_HOST='master',
   MASTER_USER='repl',
   MASTER_PASSWORD='...',
   MASTER_USE_GTID=slave_pos,
   MASTER_SSL=1,
   MASTER_SSL_CERT = '/vagrant/files/x509/slave-cert.pem',
   MASTER_SSL_KEY = '/vagrant/files/x509/slave-key.pem',
   MASTER_SSL_CA = '/vagrant/files/x509/ca-cert.pem',
   MASTER_SSL_CRL = '/vagrant/files/x509/crl.pem';

gives this on SHOW SLAVE STATUS:

MariaDB [(none)]> show slave status\G
*************************** 1. row ***************************
                Slave_IO_State: Waiting for master to send event
                   Master_Host: master
                   Master_User: repl
 ...
            Master_SSL_Allowed: Yes
            Master_SSL_CA_File: /vagrant/files/x509/ca-cert.pem
            Master_SSL_CA_Path: 
               Master_SSL_Cert: /vagrant/files/x509/slave-1-cert.pem
             Master_SSL_Cipher: 
                Master_SSL_Key: /vagrant/files/x509/slave-1-key.pem
         Seconds_Behind_Master: 0
 Master_SSL_Verify_Server_Cert: No
...
                Master_SSL_Crl: /vagrant/files/x509/ca-cert.pem
            Master_SSL_Crlpath: 

The master.info file correctly shows the file name given to Master_SSL_Crl in CHANGE MASTER TO though.

I tried to find in the code where this goes wrong, but all uses of the ssl_crl field in replication related code look correct to me ... :o



 Comments   
Comment by Hartmut Holzgraefe [ 2022-04-27 ]

May be related to https://bugs.mysql.com/bug.php?id=70866

Generated at Thu Feb 08 10:00:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.