Post by steve on Apr 10, 2014 18:56:18 GMT 1
I'm sure many of you have read or heard about the recent discovery of data leaks from 2/3 server on the internet.
In a nutshell, the Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).
The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.
More details can be found here heartbleed.com/
According to Consumerist
Just to put you at ease, it seems that the data leak is not very likely to affect individual users, but more corporate servers that store this data on their servers.
Our forum service (Proboards) has confirmed they are not affected.
It is possible to check most sites you may use to establish their vulnerability here
www.ssllabs.com/ssltest/index.html
It's still practically impossible to tell what, if any, data has been exploited (unless you work for the NSA) so in the interim, if anyone suspects a site they use (especially financial institutions or those using sensitive personal data), we cannot stress this enough.
In a nutshell, the Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).
The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.
More details can be found here heartbleed.com/
According to Consumerist
Because OpenSSL is used widely all across the Internet, it’s hard to tell who’s been affected and whether or not a site has fixed the issue. The first thing you can do is of course, check all your accounts for any suspicious activity and change your password.
Try to avoid security risks like shared Wi-Fi networks, which can allow attackers easier access to your information if they’re sharing a network with you.
Try to avoid security risks like shared Wi-Fi networks, which can allow attackers easier access to your information if they’re sharing a network with you.
Just to put you at ease, it seems that the data leak is not very likely to affect individual users, but more corporate servers that store this data on their servers.
Our forum service (Proboards) has confirmed they are not affected.
It is possible to check most sites you may use to establish their vulnerability here
www.ssllabs.com/ssltest/index.html
It's still practically impossible to tell what, if any, data has been exploited (unless you work for the NSA) so in the interim, if anyone suspects a site they use (especially financial institutions or those using sensitive personal data), we cannot stress this enough.
!!CHANGE YOUR PASSWORDS!!
I will leave this thread as a sticky for a few days, as I would like you all to be aware & I want you all to be able to surf safe in the knowledge your data isn't being intercepted (government agencies aside).
Thanks for reading
s
Thanks for reading
s