Server Should Not Examine for Certs when skip-ssl
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Activity
Show:
Julia Vural March 4, 2025 at 9:08 PM
It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.
George Lorch August 29, 2019 at 6:28 PM
Ahh, right. Nevermind
Jervin Real August 29, 2019 at 6:09 PM
if I'm not mistaken upstream compiles with YaSSL, I did not test it there. Let me know if I should, thanks.
George Lorch August 29, 2019 at 5:53 PM
upstream?
Lalit Choudhary August 29, 2019 at 1:15 PM
Hi Jervin,
Thank you for the report.
Test:
removing all ssl certificates and starting mysql with skip-ssl option.
When SSL is explicitly disabled, the server's behavior is still to check validity of existing certs in the data directory.
If the certs are corrupt, the server will not start - we have seen this in the past during node failure i.e. power failure, CPU errors, etc where the auto generated certs will get corrupted and the server will not start.
Also, when SSL is explicitly disabled, and auto generate certificates are enabled too, certs are still generated.
I think an acceptable behavior is to simply abort any SSL related checks like above when SSL is explicitly disabled.
Sample crash cases are:
Percona #242379
https://bugs.mysql.com/bug.php?id=70115