-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
mysqldumpsecure.cnf generation broken by a "&" in mysql pw #540
Comments
Hello, That is likely a problem with mysqldump, and not directly devilbox. However, you should be able to try a couple things:
|
Thanks for getting back to me @science695. I think I might have perhaps been less clear in my original post than I'd have liked. My example password wasn't So my .env file would look like
and when I set my password to that my
Escaping attemptsNow, on your suggestion I tried wrapping my password in .env with single quotes, double quotes, and backslash escaping the "&". Here are my results No quotes and backslash
But mysql doesn't connect! (Failed to connect: Access denied for user 'root'@'172.16.238.10' (using password: YES)) Double quotes no backslash
mysql also doesn't connect Double quotes and backslash
mysql also doesn't connect Single quotes and backslash
mysql also doesn't connect Single quotes no backslash
and I'm not able to log in to look at /etc/mysqldump-secure.cnf, because this causes some serious problems with devilbox. trying to access the intranet gives this message
So it looks to me as if there is inconsistent or faulty escaping of the value of MYSQL_ROOT_PASSWORD in the .env file. Do you agree? |
This is a very valid point and I have already identified the problem. It is caused by |
Does that mean it should be double or triple backslashed? \& or \& or \\& |
It should be quoted by the So best is to fix the sed side and ensure everything is as typed to the user. |
@erythro to not keep you blocked at the moment, the current work-around is to not use a |
Has been properly addressed in Release v1.0.1 https://github.com/cytopia/devilbox/releases/tag/v1.0.1 |
I guess the error still persist in latest version. I changed mysql password (root) thru phpmyadmin interface... then updated .env MYSQL_ROOT_PASSWORD=****@#$ (same password as mysql root). |
ISSUE TYPE
Checklist
.env
file is attacheddocker-compose.override.yml
is attached (if it exists)cfg/
dir are attached (if customized)docker-compose logs
andlog/
output is addedOS / ENVIRONMENT
SUMMARY
I'm not going to reveal my mysql password, but say it was
before&after
my mysqldump-secure.cnf would look like this:So running mysqldump-secure.cnf gives an error.
STEPS TO REPRODUCE
Set your mysql password to something containing an "&" character.
I set the mysql password in Heidisql (my sql client), and in the .env config
EXPECTED BEHAVIOUR
/etc/mysqldump-secure.cnf password section set with my password
ACTUAL BEHAVIOUR
/etc/mysqldump-secure.cnf looking the way it does in the summary.
OTHER INFORMATION
Start command
The text was updated successfully, but these errors were encountered: