Yes this is a bit dated, yet even more relevant a topic in today's world of Wordpress, Joomla, OsCommerce, Discussion forums, and all other types of CMS's and CRM based dynamic, database driven websites.

I'm offering it up here for the community to glean some insight from, and also for the feather in my cap, as a shameless plug touting some of the things I'm especially proud of having contributed in the past.

Just because it's dated, doesn't mean it's not wholly relevant.

Besides, it's still a good and entertaining read



http://digg.com/security/Mr_Propelle...Securing_MySQL

Indeed it's (still) valid in the sense of a generic warning when using anything PHP-based and if it was dated in just the actual date sense I'd have no problem with that. Unfortunately http://maxdev.com/PrintArticle283.phtml is dated in that it exposes only one single facet of what hardening a system and LAMP stack is about. This is best illustrated if you look at the list of CVE's for the product you describe: http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=MD-Pro.

Hardening MySQL is recommended always but it is not the only measure one should take.