On Wed, 2008-01-30 at 10:36 -0600, John Goerzen wrote: > Hi James, > > Thanks for sending this along. > > I'm not sure the proposal is right. From the source of make_catalog_backup: > > # This script dumps your Bacula catalog in ASCII format > # It works for MySQL, SQLite, and PostgreSQL > # > # $1 is the name of the database to be backed up and the name > # of the output file (default = bacula). > # $2 is the user name with which to access the database > # (default = bacula). > # $3 is the password with which to access the database or "" if no password > # (default ""). WARNING!!! Passing the password via the command line is > # insecure and should not be used since any user can display the command > # line arguments and the environment using ps. Please consult your > # MySQL or PostgreSQL manual for secure methods of specifying the > # password. > # $4 is the host on which the database is located > # (default "") > > By having the first two as they are, we have a configuration that could at > least work by default with some PostgreSQL databases. > > I think that perhaps the best solution is to mention in README.Debian that > this line will likely need to be modified during installation. > > Not just that, but there are better, database-specific, ways to pass along > passwords.
Hi John, It's obviously up to you whether to apply the patch, and I was simply forwarding it, so I don't mind one way or the other. However, I think a note in README.Debian would be a good start either way. Thanks, James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
