Fix regression on 'COM_CHANGE_USER' for 'mysql_native_password' - Closes #4589 #4623
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#4589 Fixes handing of 'COM_CHANGE_USER' for 'mysql_native_password' when using hashed user passwords.
- Improved test documentation and logging format. - Added extra options checking invalid passwords and hashed passwords. - Improved combinations on options being check.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a regression introduced in
v2.6.0that breaks the handling ofCOM_CHANGE_USERformysql_native_passwordwhen hashed passwords are used. This is, when passwords for users are set hashed onmysql_userstable, for example, making use ofMYSQL_NATIVE_PASSWORD()for hashed password generation.