Heartbleed’s Heartache
Page 1 of 1
Heartbleed’s Heartache
AKMARK5000 Thu Apr 10, 2014 2:26 pm
Heartbleed’s Heartache:
The intention of this article is not to provide “all encompassing information,” but rather an “FYI” or opinion “PSA” type of writing.
Heartbleed is a vulnerability of Open Source SSL software that is used by some common websites or web services. It has been plastered all over the news, sensationalized by some media and even used as a “scare tactic” by the unscrupulous few. There’s a potential, not a certainty, for digital thieves and hackers to gain access to private data such as credit card information and passwords. Not to trivialize to seriousness of Hartbleed, I’m just saying there’s little if any reason for the average end-user or customer to over react, go into panic mode or go ballistic over it.
Most websites or web services affected by the Heartbleed issue have already taken appropriate measures to fix the issue for their customers such as Google, Gmail, Amazon and Yahoo Mail. But if the issue is fixed at a certain website or web service, it becomes the customers’ responsibility to reset or change their own passwords. Finding out whether or not a website or service is affected is pretty simple…
==> http://filippo.io/Heartbleed/
As a second opinion or if the above does not work out, is to try the blow link. The below links up to a simple chart describing which sites require you, the customer, to change passwords or security measures.
==> http://mashable.com/2014/04/09/heartbleed-bug-websites-affected/
If you do a lot of business transactions on the web or provide web based services such a accepting payments or trading and use Open Source SSL software, well, it’s time to scramble and patch your servers, change passwords and alert your customers.
The intention of this article is not to provide “all encompassing information,” but rather an “FYI” or opinion “PSA” type of writing.
Heartbleed is a vulnerability of Open Source SSL software that is used by some common websites or web services. It has been plastered all over the news, sensationalized by some media and even used as a “scare tactic” by the unscrupulous few. There’s a potential, not a certainty, for digital thieves and hackers to gain access to private data such as credit card information and passwords. Not to trivialize to seriousness of Hartbleed, I’m just saying there’s little if any reason for the average end-user or customer to over react, go into panic mode or go ballistic over it.
Most websites or web services affected by the Heartbleed issue have already taken appropriate measures to fix the issue for their customers such as Google, Gmail, Amazon and Yahoo Mail. But if the issue is fixed at a certain website or web service, it becomes the customers’ responsibility to reset or change their own passwords. Finding out whether or not a website or service is affected is pretty simple…
==> http://filippo.io/Heartbleed/
As a second opinion or if the above does not work out, is to try the blow link. The below links up to a simple chart describing which sites require you, the customer, to change passwords or security measures.
==> http://mashable.com/2014/04/09/heartbleed-bug-websites-affected/
If you do a lot of business transactions on the web or provide web based services such a accepting payments or trading and use Open Source SSL software, well, it’s time to scramble and patch your servers, change passwords and alert your customers.
AKMARK5000- Posts : 216
Join date : 2010-04-01
Age : 51
Location : Central NYS -
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum|
|
|