MySQL Bugs: #49977: Passwords containing special characters are not handled

Bug #49977	Passwords containing special characters are not handled
Submitted:	29 Dec 2009 14:25	Modified:	11 Jan 2010 13:47
Reporter:	Louis Breda van	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.11	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	backups, passwords, Special Characters

Description:
Hello,

When trying to create backups using the workbench "export to disk" function, that "Operation failed with exitcode 1".

Tryed to find the problem, I entered the command found in the log directly on the command line.

I got the same problem unless I quoted the special character containing password with string quotes "<password>".

Knowing that, I did create a DB user with a simple password not containing special characters and defined a new connection using that user,

That turned out to be the work arround.

However, my passords especially my root paswords, allways contain special characters ........ (I would like to keep it that way :>)

 

How to repeat:
As described, just use a pasword containing special characters like :!?&@~ etc

Suggested fix:
modify the code to quote the command towards mysqldump.exe and probably also on other places.

Sincerely,

Louis

Hello,

I noticed that the problem is not only related to passwords but also to e.g. file names.

The workbench (e.g. dump restore) does not work correctly when a file name contains e.g. blanks.

Sincerely,

Louis

You guys are lifesavers, if this bug wasn't logged here I'd have been left hanging. When I did an import from self-contained (.sql) backup file I would get a failed import with 'exitcode 1'.

If I tried to import from a backup project folder (a large number of .sql files) I would get 'exitcode 2'.

In the 'Backup Project Folder' case my full path to the files was in a folder with spaces 'C:\SVN\privateprojectname\data backups\Backup 20091231'.

When I did the 'Self-Contained' import the file had spaces in the name AND was in the aforementioned folder with spaces.

My root password included a "!" character (no spaces) and that didn't seem to have any impact. I know this because once I removed spaces from the self-contained backup I was able to import successfully without changing my root password.

I hope this helps, definitely looking forward to the current build reaching a stable status.

Dylan, Inno Software Inc.
http://www.innosoftware.net

Many thanks for writing a bug report.

I will set this here as duplicate of bug #50213 because there you already will find the analysis of this problem and we also already started the internal discussion of fixing it.

Regarding the filename bug, this can be avoided by using DOS style filenames when loading the file/folder, e.g. replacing C:\Your Folder Name\ with C:\YOURFO~1\

Sigh! :-(

(just a comment to the previous comment. The problem here is not with Windows, but with Workbench using some unix-based library/ies that does not realize that Windows is fully Unicode-compliant OS).

Please understand that Windows 95 is dead for 10 years!