-
Notifications
You must be signed in to change notification settings - Fork 986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New 'mysql_servers_ssl_params' settings not working (TLS/SSL error: invalid directory) #4466
Comments
Hi @brogon . |
If values in mysql_servers_ssl_params are empty strings, they needs to be passed as NULL arguments in mysql_ssl_set() and mysql_options() Closes #4466
Thanks for looking into it! In my search of the issue, I've found three other places besides the central "MySQLConnection" class, which seem to create backend connections - the As I'm not sure in which context these are used, but you might want look into these, too, and decide if they also need the "ssl_params" logic. I'd think the "main" function is OK, as it only "bootstraps" a given database, but killing queries and monitoring might "benefit" from it... |
ssl_params: use NULL instead of empty string #4466
ProxySQL version: 2.6.0
OS version: n/a, Docker image "proxysql/proxysql:2.6.0"|
When using "mysql_servers_ssl_params" instead of the global variables, ProxySQL can't use the given files.
If only given "ssl_ca", the "file open" error is just ignored, resulting in certificate validation issues if using a custom CA. If you use "ssl_cert" and "ssl_key" for cert-based authentication, it fails with "TLS/SSL error: invalid directory".
I've created a docker-compose based demonstration environment; you can find it attached to this report. It contains the needed configuration (proxysql.cnf and certificate/key-files) to reproduce the issue.
proxysql_ssl_params_test.zip
proxysql_ssl_params_test.tar.bz2.zip (zipped .tar.bz2 to re-create the correct permissions on Linux)
The complete log of a failure from the aforementioned environment:
The text was updated successfully, but these errors were encountered: