The "Heartbleed" Bug

  • Thread starter DRIFT3R_X7
  • 19 comments
  • 1,072 views
326
United States
Hudson, WI
DRIFTER_X7
heartbleed.png
I feel that now would be a good time to talk about what is going on around the internet these days. If you didn't know, there is a new bug going around the internet, known as 'Heartbleed'. A link for more info about Heartbleed can be found here. So... anyone got any opinions about this?

List of every company affected by Heartbleed can be found here: https://github.com/musalbas/heartbleed-masstest/blob/master/top1000.txt
 
Last edited by a moderator:
So on the one hand sites are saying change your password because of this, on the other hand they are saying that changing it now whilst all the spotlight is on it will make it even more likely your new one will be stolen. :ouch:

And this bug has been around for 2 YEARS.... epic fail.
 
On a less serious note... who actually uses Yahoo mail? It's the most insecure mail server in existence. Half the people I know who Yahoo have had their accounts hacked, and that was before Heartbleed became possible...
 
I'm glad I don't have either my bank account or Paypal account linked to my Yahoo email account, then. :lol:
 
I use yahoo mail :lol:
But only for stuff like gaming, forums,...
I have so many mail accounts, from gmail to yahoo to my own mail server

I had my account hacked once in all the 15 years using yahoo. 1 account out of 10 I have on yahoo.
Ever since I have a computer, I never have gotten my system infected.
That's the most common problem, so many people having old anti-virus, no firewall and the computer full of trojans. That's the most common way, pw get stolen.

And even if something happens, as I don't act careless (secure p/w, always different p/w,...), my bank will always give me my money back.

But this man made bug is really big. Facebook, Steam,... so many high profile sites...
 
Last edited:
So on the one hand sites are saying change your password because of this, on the other hand they are saying that changing it now whilst all the spotlight is on it will make it even more likely your new one will be stolen.
You should only change your password if you know the site in question has upgraded their OpenSSL stack AND they changed their SSL certificate (including keys) after upgrading.
 
You should only change your password if you know the site in question has upgraded their OpenSSL stack AND they changed their SSL certificate (including keys) after upgrading.

Has Yahoo been fixed? I don't know if they have taken action yet.... you would think so being such a big company.
 
Not surprising that we'd be hearing something like this. Whether it's actually true or not, the agency would deny it; we all know that. And regardless of the evidence (which right now is pretty much unsourced rumors) a lot of people would believe they were involved.

Myself, I don't know. But I regret to say I do find it believeable.
 
It's very easy to prove they were at least not responsible for it, since commit logs for OpenSSL are public. Did they use it when they found out? Probably yes.
 
It's very easy to prove they were at least not responsible for it, since commit logs for OpenSSL are public. Did they use it when they found out? Probably yes.
Do you personally know the backgrounds of everybody who made a commit to the the code? I surely don't.

I do agree with you, though, that the NSA (probably) wasn't responsible for planting the bug although I certainly don't rule out the possibility. However, the more I read about this the more convinced I become that the NSA knew about the bug very early on.

For those who may not understand how the bug works, here's one of the best explanations I've seen yet:

EDIT:
Nevermind, treed by @niky!
 
Do you personally know the backgrounds of everybody who made a commit to the the code? I surely don't
You don't have to, many other people do know the people in these open source communities. In this case it's a German developer that fixed many issues and bugs before introducing a new one because he (and the code reviewer) missed a validation check.
 
im a bit slow about this, so basically what does this bug do ?

Exactly what the comic in Post #15 states. You can query a server to see that it's still there. The server returns the canned response you ask it to send, but you can trick it to send much, much more information than that.

All you have to do is sift through the information sent back and you can glean passwords, credit card numbers and a whole lot of other stuff.
 
Back