Tuesday 31 January 2017

Internet Explorers Warn about insecure connections.


Insecure Connections 


Living on-line is another word to our day-to-day life in this 21st century, we live in the world of online registrations and payments. A lot of forms are being filled-in on daily basis online. It has become an integral part of our life.

It is so common that the average user hardly thinks about the security of personal data being sent or pays a deaf ear to the warnings. 

While most of the larger companies provide their clients with a secure encrypted HTTPS connection – every now and then you can still stumble upon a form in HTTP. 

This could lead to a serious data leakage – from a password on a forum to your social security or credit card number being stolen. 

Both Google and Mozilla integrated more prominent HTTP warnings in the recent updates for their respective browsers.

Firefox Warning



This feature has already been applied in the beta version of the latest Mozilla browser but with the recent official release of Firefox 51, it became available to a much larger number of users. 

Going forward every time you come across an HTTP page asking for a password you will see a grey padlock crossed with a red strike. 

If you click on the padlock you’ll see a warning: “Logins entered on this page could be compromised.” 

This is a much welcomed change as previous versions of Firefox simply lacked such a feature – displaying a green padlock for protected HTTPS connections and no notification for HTTP whatsoever.



chrome warning


Google Chrome has taken a similar but with a more clear approach. The browser displays an information icon with a note “Not secure” in case of a not trustworthy HTTP connection. 

This warning appears not only for HTTP sites asking for login or password information but also anytime your credit card details are required. 

This is just another step in preventing personal data leakage for Google Chrome users. Further plans include displaying such a warning in incognito mode and eventually labeling all HTTP pages as not secure.


No comments:

Post a Comment