Hi Alexander, I just want to piggyback on this issue. I get a similar error
9:57:44 am
Failed to backup “BU” folder in “C:\BU”. #[JOB-BAK:2009] Failed create archive.
9:57:26 am
Failed to backup “dm8744025311084” database with “Full” backup type: mysqldump: [Warning] Using a password on the command line interface can be insecure. mysqldump: Couldn’t execute ‘show events’: Access denied for user ‘xxxxxxxxxxxx’ to database ‘dm8744025311084’ (1044)
That error message is generated by MySQL Server and we can do nothing here from our side. Please try to resolve the issue using the recommendations from the previous replies or try to find more information on the web.
We get a related error from our security monitoring group: password on the commandline.
This is the observation:
cmd"" /Q /C “”““C:\Program Files (x86)\SQLBackupAndFTP\DBMS\MySql\mysql.exe”” --host ourmysqlserver --port 3306 --user ““backupandftp”” --password [REDACTED] --html --connect-timeout 30 --execute ““SHOW DATABASES;”” “”
We use the option password via environment var, but the password is still visible.
My question is:
Is there any plan to support more secure authentication methods, such as:
MySQL Login Path (mysql_config_editor )
--defaults-extra-file / MySQL option files
Windows Credential Manager
Any other mechanism that avoids passing passwords on the command line?
Many organizations have security policies that prohibit credentials from appearing in process command lines. At the moment, this seems to make SQLBackupAndFTP unsuitable for environments with these requirements.
I would appreciate any feedback from the development team on whether support for one of these authentication methods is planned or already available.