-
Notifications
You must be signed in to change notification settings - Fork 88
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
mysql_user: Drop support for REQUIRESSL #101
Comments
I don't feel empowered to discuss the topic not being a MySQL user even (would be pretty dangerous to make any breaking decisions based on my suggestions, among other thing) |
I don't feel empoyered to discuss the topic not being a MySQL user even (would be pretty dangerous to make any breaking decisions based on my suggestions, among other thing) |
I doubt most of sysadmins use REQUIRESSL with MySQL / MariaDB, even though it's recommended. I'm fine with this approach. |
Besides that it's nice to finally get rid of the "SSL" (and replace it with the correct "TLS"), since TLS is around for almost 22 years now (as successor to the SSL protocols) and the last SSL protocol (SSLv3) has been deprecated almost 6 years ago (after being broken, and not being recommended for many more years). :) |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
The
REQUIRESSL
privilege has been superseded by the more completetls_requires
option. The privilege has been kept for backwards compatibility, but in doing so it's introduced extra complexity in the module code and a number of idempotence issues.With PR #97 we're planning a release with breaking changes. Here I'm proposing using the opportunity to drop the support for the
REQUIRESSL
privilege in the same breaking release.The text was updated successfully, but these errors were encountered: