View Full Version : Heartbleed

04-08-2014, 11:37 PM
Public service announcement: If you own or run any Linux web servers, cloud or dedicated, that use https, then upgrade your version of openssl immediately, restart all open files, then re-issue your SSL certificates with new private keys.

Process: Determine if your version of SSL is vulnerable:

lsof -n | grep ssl | grep DEL

If any running programs show up in the list, you're going to need to...

yum clean metadata && yum update openssl


apt-get update && apt-get install openssl

Then run that original lsof command and restart EVERYTHING that shows up on the list. Then you can replace your certificates and key.

For git lovers, there's this repo for testing (https://gist.github.com/takeshixx/10107280) vulnerable port 443s from the outside, if you also like python.

End public service announcement, though this is what happens when you update your libraries to counter one theoretical BEAST attack (http://market-ticker.org/akcs-www?post=228919) and make yourself vulnerable to something much more serious.

04-10-2014, 10:19 AM
When you visit a website for the first time since you learned about the Heartbleed bug, consider changing your password for that site, if any, as the first thing to do on site.

04-23-2014, 02:07 PM
Kim Komando reports that several experts say that Heartbleed is beyond repair. We need to change to another SSL model. http://www.komando.com/blog/249665/heartbleed-is-beyond-repair-according-to-experts?utm_medium=nl&utm_source=notd&utm_content=2014-04-23-article_3-cta