John offers a broad overview of MySQL security. He does not cover everything, but provides a good intro for someone new to MySQL. Here are some notes from his talk:<\/p>\n
Security Priorities:
\n– Data not stolen or tampered with.
\n– only access data that you’re authorized to access
\n– secure passwords<\/p>\n
– host level security
\n – obviously dont run MySQL as a privledged user.
\n – patch system regularly<\/p>\n
– net security
\n – bind to localhost or skipnetworking unless you have remote clients
\n – firewalls
\n – use ssl
\n – what kind of load does ths add<\/p>\n
– authentication in mysql
\n – 4.1 includes a new auth scheme with more secure password hashes.
\n – 4.1 supports old protocols, but new protocol is highly recomended.
\n – SSL support from slaves to marster, clieent to server, etc.
\n – grant can now allow you to require certs, issuers, specific ciphers, etc.
\n – limit connections, qeuries, reads, writes, etc per hour.<\/p>\n
views:
\n – you can create views so that a specific user only sees rows that meet his privs \/ restrictions.<\/p>\n
– Groups \/ Roles, are recognized as necessary by MySQL developers. They hope to include them in 5.1, but make no guarantees.<\/p>\n
– ideas for web app users:
\n – give each script\/object\/method a user name so that for security and logging reasons which scripts did what, see who is connected,
\n– interactive help now included in MySQL!
\n – ex: help grant types<\/p>\n
– MySQL “worm” of Jan ’05
\n The MySQL work would scan tcp port 3306 on the public net and then attept to brute force root. It had a very small list of common passwords and managed to sucessfully connect to an alarming number of servers. The worm would then create a table with a blob column where it would insert the words code. It would then dump itself to a DLL file and drop the table. Then by creating a function it can run itself via mysql. <\/p>\n
The worm did not last long as the connecting zombies caused a DOS attack on the IRC servers where the zombied nodes were managed,<\/p>\n
– MySQL 4.1 now includesfeatures to make this more difficult:
\n – User defined functions must define and meet certain criteria or they will be considered “suspicious” and not run.
\n – root@ accounts were reomved from windows, no other distros ever had them.
\n – wont let you use .. or other pathname info in the name of a shared object<\/p>\n","protected":false},"excerpt":{"rendered":"
John offers a broad overview of MySQL security. He does not cover everything, but provides a good intro for someone new to MySQL. Here are some notes from his talk: Security Priorities: – Data not stolen or tampered with. – only access data that you’re authorized to access – secure passwords – host level security […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[8],"_links":{"self":[{"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/posts\/125"}],"collection":[{"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/comments?post=125"}],"version-history":[{"count":0,"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/posts\/125\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/media?parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/categories?post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fonz.net\/blog\/wp-json\/wp\/v2\/tags?post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}