Quote:
Originally Posted by cd34
This was my fault. Mysql released a security advisory, that particular machine showed that the exploit had been attempted unsuccessfully (along with two other machines) and we upgraded it to the suggested 'secure' release of mysql. However, the release that was suggested contains the following bug:
http://bugs.mysql.com/bug.php?id=32202
A regression bug like this shouldn't occur in mysql -- and it wasnt expected, and I apologize. Machines are upgraded quite frequently due to security patches and while I did do quite a bit of internal testing on mysql on two of our test machines, neither would have hit that particular bug. We've downgraded mysql and applied a workaround for now.
Normally for security updates, we don't really make announcements because each machine probably gets 3-4 security patches a week applied. However, we will include a blog of sorts that lists updates made to machines to at least make diagnosing things like this go a little quicker.
Again, I do apologize. |
My concern was not with you but the fact that my personal slave and tech support guru wasn't available. Coupled with the fact that almost none of what you said means anything to me, makes me think I really need to read "Web terms for Dummys" but thanks for the apology, our client is a MAJOR chore..
Sparky threw himself >>> |bus|