[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re[2]: [cobalt-users] Re: MySql
- Subject: Re[2]: [cobalt-users] Re: MySql
- From: Richard Kurth <rkurth@xxxxxxxxxxxx>
- Date: Fri Jan 5 19:16:01 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Hello Brent,
Thursday, January 04, 2001, 10:00:22 PM, you wrote:
BS> On Thu, 4 Jan 2001, Richard Kurth so wrote:
BS> } the run GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,REFERENCES,DROP,INDEX,ALTER
BS> } ON userdatabase.* TO 'username'@'domain.com' IDENTIFIED BY 'password
BS> No insult intended or implied, keep on helping but this
BS> is a very very - EXTREMELY bad idea. MySQL DROP priviliges are
BS> server wide, that is, any user with DROP priviliges can DROP any
BS> database on that server, including the database in which MySQL
BS> privledges are stored. While not nearly as easily abused, good
BS> MySQL Admins are very careful about who they grant GRANT, ALTER,
BS> FILE, SHUTDOWN and PROCESS priviliges to as they too can easy and
BS> will be used against you.
BS> This is all clearly explained in the "Privileges provided by
BS> MySQL" section of the MySQL user manual. If you are going to run a
BS> MySQL server that can be accessed by users my opinion is that you
BS> really ought to at least think about reading the entire section
BS> mentioned above very carefully, at least twice, before you even
BS> think of putting that server on line.
What you say is true and I would never give anybody on my server
the drop privilege. However in his original e-mail he asked how to
give them the ability " to create and admin their own databases".
So that is what I told him I also send to read the manual.
--
Best regards,
Richard mailto:rkurth@xxxxxxxxxxxx