Re: What does this mean - Mark Maggelet - com.mysql.lists.mysql

5 messages in com.mysql.lists.mysqlRe: What does this mean

From	Sent On	Attachments
Charles L Hagen	16 Mar 2001 07:12
Hardy Merrill	16 Mar 2001 08:09
Mark Maggelet	16 Mar 2001 09:49
Hardy Merrill	16 Mar 2001 10:34
Mark Maggelet	16 Mar 2001 10:53

Subject:	Re: What does this mean
From:	Mark Maggelet (magg...@mminternet.com)
Date:	03/16/2001 10:53:32 AM
List:	com.mysql.lists.mysql

On Fri, 16 Mar 2001 13:35:18 -0500, Hardy Merrill (merr...@missioncriticallinux.com) wrote:

Sure it's easier, but which is safer?

I don't have Charles first message on this topic, but I believe his error message was from logrotate which is a cron job. If Charles put

mysqladmin -uuser -ppassword

into a cron job, then the user's(root?) password would be in open view to anybody who could view the crontab - granted, you would have to be root to view the root crontab, but putting the password to the MySQL user right in the cron command is just a little too "loose" for me. A safer method would be to "hide" the user/pw in the Unix user's home directory in the ..my.cnf file, as I outlined below.

Uh... root can read those too. If you're imagining a situation where someone just rooted you in order to get access to MySQL, I guess it's possible that doing it this way will slow him down by about 5 minutes, but I don't really think it's an issue.