- 326
- Hudson, WI
- DRIFTER_X7
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:
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.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.
Do you personally know the backgrounds of everybody who made a commit to the the code? I surely don't.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.
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.Do you personally know the backgrounds of everybody who made a commit to the the code? I surely don't
im a bit slow about this, so basically what does this bug do ?