{"id":2432,"date":"2012-07-20T15:25:44","date_gmt":"2012-07-20T20:25:44","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/?p=2432"},"modified":"2012-07-20T15:25:48","modified_gmt":"2012-07-20T20:25:48","slug":"security-fixes-in-mysql-critical-patch-updates","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2012\/07\/20\/security-fixes-in-mysql-critical-patch-updates","title":{"rendered":"Security fixes in MySQL & critical patch updates"},"content":{"rendered":"

This is the third time MySQL has made an entry into the Oracle Critical Patch Update Advisory<\/a> service. The first time, we at Team MariaDB<\/a> came up with an analysis:\u00a0Oracle\u2019s 27 MySQL security fixes and MariaDB<\/a>.<\/p>\n

Security is important to a DBA. Having vague explanations does no one any good. Even Oracle ACE Director Ronald Bradford<\/a> chooses to ask some tough questions<\/a>\u00a0on this issue. Recently we found a bug in MySQL & MariaDB and did some responsible disclosure<\/a> as well.\u00a0<\/p>\n

Security is a big deal to distributions shipping MySQL. It comes alongside having a good, accessible bugs system. Recall a discussion<\/a> a while back about possibly even replacing MySQL with MariaDB (this led to a fun discussion and a long meeting at UDS Oakland to ensure choice).<\/p>\n

These discussions always come back. Today on the Debian mailing list, the suggestion popped back up again<\/a>. I’m sure it will pop up again in October when the next CPU includes some fixes in MySQL…<\/p>\n

What is Oracle going to do about this? Will it start being more open (not with a select few folk, but with the wider community)?<\/p>\n

Share this:<\/h3>