Bug #113777 | Replication with SSL certificates fails after upgrade to MySQL 8 | ||
---|---|---|---|
Submitted: | 26 Jan 2024 14:24 | Modified: | 2 Feb 2024 15:52 |
Reporter: | IGG t | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Security: Encryption | Severity: | S3 (Non-critical) |
Version: | 8.0.36 | OS: | Windows |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
Tags: | replication, SSL |
[26 Jan 2024 14:24]
IGG t
[29 Jan 2024 11:49]
MySQL Verification Team
Hi Mr. t, Thank you for your bug report. However, it is not a bug ...... For 8.0, you have not defined your certifications correctly. This is what's wrong": master_SSL_CERT='C:/MySQL/ssl/client-cert.pem', master_SSL_KEY='C:/MySQL/ssl/client-key.pem'; Please, follow these instructions: https://dev.mysql.com/doc/refman/8.0/en/replication-encrypted-connections.html. For two servers you need 2 sets of certs. Also, you do not need the [client] , that you are using. Next, please note that mysql_ssl_rsa_setup will soon be deprecated. Difference is that, unlike 5.7, 8.0 is now doing more to validate that the correct certs are used everywhere. And you have not done that . Not a bug. Not a Bug.
[2 Feb 2024 15:52]
IGG t
Thanks, however you say I have not defined my certifications correctly and to follow the instructions. But from what I can see the instruction simply says: ssl_ca: The path name of the Certificate Authority (CA) certificate file. (ssl_capath is similar but specifies the path name of a directory of CA certificate files.) ssl_cert: The path name of the server public key certificate file. This certificate can be sent to the client and authenticated against the CA certificate that it has. ssl_key: The path name of the server private key file. Which from what I can see, is exactly what I have: source_SSL_CA='ca.pem', source_SSL_CAPATH='C:/MySQL/ssl', source_SSL_CERT='C:/MySQL/ssl/client-cert.pem', source_SSL_KEY='C:/MySQL/ssl/client-key.pem';