failures to execute drush will show the mysql root password in logs

I had a peculiar situation here where the provision module for the d6 platform was running HEAD, which created communication problems with the frontend. That issue was fixed simply by updating to the right branch. However, the resulting log was disconcerting:

The command could not be executed succesfully (returned: PROVISION_OUTPUT>>>a:4:{s:4:"site";a:33:{s:9:"client_id";s:1:"1";s:12:"client_email";s:19:"webmaster@localhost";s:5:"db_id";s:1:"2";s:7:"profile";s:7:"default";s:7:"site_id";s:3:"562";s:8:"language";s:2:"en";s:8:"site_url";s:20:"www.aidi.koumbit.org";s:9:"task_type";s:6:"backup";s:7:"site_ip";s:9:"127.0.0.1";s:9:"site_port";i:80;s:7:"db_type";s:6:"mysqli";s:7:"db_host";s:9:"localhost";s:9:"db_passwd";s:10:"egnftht39D";s:7:"db_name";s:8:"site_562";s:7:"db_user";s:8:"site_562";s:9:"installed";b:1;s:11:"backup_file";s:64:"/var/hostmaster/backups/www.aidi.koumbit.org-2009-01-23_2.tar.gz";s:7:"aliases";a:1:{i:0;s:5:"Array";}s:4:"root";s:26:"/var/hostmaster/drupal-6.x";s:7:"backend";b:1;s:9:"master_db";s:46:"mysql://hostmaster_root:***CENSORED***@localhost";...

Notice the mysql root password in there. This shouldn't happen. Basically, a lot more care should be given to that information and we should refrain as much as possible from passing it around, even through pipes.