Add support for "login paths" in both MySQL and MariaDB #8
Conversation
This file contains hidden or 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
* Removes support for dumping flush logs. * Changes default for "usessl" config from "yes" to "no" and adds support for SSL options in MySQL 5.6 and higher. * Added support for "login paths" https://dev.mysql.com/doc/refman/5.6/en/option-file-options.html#option_general_login-path instead of setting password in config file. * Fixes "du" and "sed" commands failing in MacOS. * Also dump events to backup. * Removes some debug print statements.
Kekos
force-pushed
the
mariadb-login
branch
from
1257c06 to
31cad9e
Compare
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
To avoid the "Using a password on the command line interface can be insecure" warning in MySQL, support for login path was added in an other repository.
I recently changed to MariaDB on one server, which have no such solution and instead suggests using extra configuration file with secure permissions.
Since this repo seemed to have "more" activity I thought it would be good to merge here.