Well a lot of concern, and rightfully so, has been made about the heartbleed bug recently.
I do not think I should try to add much more than those that I consider experts have already mentioned. If you have not reviewed the following posts you should.
It is very likely that your code repositories will have this update, at least that is what I have seen so far.
Via Fedora 20 for example
Installed 1:1.0.1e-37.fc20.1
So the steps are easy to follow, it is up to you to ensure your system is secure.
I do not think I should try to add much more than those that I consider experts have already mentioned. If you have not reviewed the following posts you should.
- http://www.mysqlperformanceblog.com/2014/04/08/openssl-heartbleed-cve-2014-0160/
- http://www.mysqlperformanceblog.com/2014/04/09/heartbleed-separating-faq-from-fud/
- http://www.mysqlperformanceblog.com/2014/04/14/advisory-heartbleed-cve-2014-0160-perconas-customers-users/
- http://www.oracle.com/
technetwork/topics/security/ alert-cve-2014-0160-2190703. html - https://www.openssl.org/news/
secadv_20140407.txt - https://lists.fedoraproject.org/pipermail/package-announce/2014-April/131221.html
- Update and secure your OS first.
- IF you use SSL with MySQL then
- Stop MySQL
- Create new certs for your connections.
- That should include new expire dates and etc.
- Start MySQL
It is very likely that your code repositories will have this update, at least that is what I have seen so far.
# yum list openssl resulted in 1.0.1e-16.el6_5.7
Via Fedora 20 for example
# rpm -q openssl
openssl-1.0.1e-30.fc20.x86_64
#yum update openssl
Installed 1:1.0.1e-37.fc20.1
So the steps are easy to follow, it is up to you to ensure your system is secure.
No comments:
Post a Comment
@AnotherMySQLDBA