The Heartbleed Bug

The Heartbleed Bug has been receiving a good amount of press over the last few days. That is because the bug has been interfering with dozens of some of the most high profile websites out there, ranging from Gmail to Facebook OKCupid to Yahoo. Due to this, it is important to know exactly what this bug is and how important to is to protect yourself from it.

Chances are, you use a service that has been affected by Heartbleed. That is because the bug is a security problem that takes place on the OpenSSL software. This allows hackers to access memory directly from data servers that use this software. Over 500,000 websites use this particular software, so many of the most popular sites on the Internet use this service. It places all user information information, such as payment data and personal material, like passwords and usernames in the hands of hackers who have used the Heartbleed bug.

OpenSSL is short for Secure Sockets Layer. It basically is a form of encryption that is used on websites in order to protect outside individuals from stealing your information. It has been used on the Internet for some time now, and while it has provided all sorts of different updates over the years, hackers were able to locate this method of accessing information from the websites that use OpenSSL.

Not all websites use OpenSSL, so not every single website is affected by it. However, it is important to know how the bug works and how it affects your personal information. The hack allows individuals to access up to 64 kilobytes of server memory in order to perform the hack over and over again. This basically allows them to take just about any sort of information they might want. This means they can take everything from usernames and passwords to cookie data that websites use to place onto your computer in order to monitor what you do online.

As of right now, it is believed that a man named Robin Seggelmann is behind the Heartbleed Bug, as he worked on OpenSSL for four years while obtaining his Ph.D. However, he did not actually create the bug, but instead wrote the glitchy code that allows individuals the 64 kilobytes of server memory. Regardless of where it came from though and how it originated, it is important for you to change just about all of your user passwords in order to ensure everything is safe.