Skip to content

check if a password column exists and only then check contents #57

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

Merged
merged 2 commits into from
Oct 14, 2020

Conversation

rndmh3ro
Copy link
Member

Signed-off-by: Sebastian Gumprich github@gumpri.ch

Fixes #52

Signed-off-by: Sebastian Gumprich <github@gumpri.ch>
Signed-off-by: Sebastian Gumprich <github@gumpri.ch>
Copy link
Member

@micheelengronne micheelengronne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good. I have a more general question though. Is it still relevant to keep compatibility for 5 years old deprecated behaviour ? mysql 5.7.6 appeared in 2015, if a system is still running with something older, I think security checks would be useless and the first thing to do would be to update.

@rndmh3ro
Copy link
Member Author

rndmh3ro commented Oct 14, 2020

You're right that we should not support deprecated behavior. However MariaDB still uses the password-column so we still need to check it. Do you have a better idea how to achieve this?

Here are the versions our supported OS'es use:

@micheelengronne
Copy link
Member

If MariaDB still needs it, the checks is usefull then.

@rndmh3ro rndmh3ro merged commit 3e262f0 into master Oct 14, 2020
@rndmh3ro rndmh3ro deleted the password branch October 14, 2020 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants