Fix using password hashes with MariaDB #55655
Merged
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
MariaDB always needs the 'PASSWORD' keyword when working with password hashes, also when ALTER USER is being used.
ghost
requested a review
from 
garethgreenaway
approved these changes
Dec 16, 2019
dwoz
approved these changes
Dec 16, 2019
xeacott
approved these changes
Dec 16, 2019
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.
I rebased PR #54343 since that was all that was needed @dwoz
What does this PR do?
Fix MariaDB user interactions.
What issues does this PR fix or reference?
#53861 and #54299 and #54343
Previous Behavior
Using password hashes as passwords
New Behavior
Doing what it's told
Tests written?
No
Commits signed with GPG?
No
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.