Google Chrome to Mark All HTTP Sites "Not Secure" Starting July 2018

[Faybert]

Google announced earlier today plans to mark all HTTP sites as "Not Secure" in Chrome, starting with July 2018, when the company plans to release Google Chrome 68.

The company's decision comes after HTTPS adoption increased among website owners and a large chunk of today's traffic is now encrypted.

Google said that more than 68% of Chrome traffic on both Android and Windows and over 78% of Chrome traffic on both Chrome OS and Mac, is now being sent via HTTPS.

Google has been preparing for this
The decision to mark all HTTP sites as "Not Secure" in the URL address bar is part of the company's larger strategy.

The first stage of this plan rolled out with Chrome 56 when Google marked all HTTP pages as "Not Secure" if the pages contained password or payment card fields.

The second stage took place with Chrome 62 when Google marked all HTTP pages opened in a Private Browsing window as "Not Secure."

July's Chrome 68 release will mark this process' third and final stage.

Google is not alone in its decision to penalize all HTTP sites. Mozilla started this trend in December last year when engineers started laying the groundwork for Firefox to mark all HTTP sites as "Not Secure" as well.

Unlike Google, the Mozilla Foundation did not announce a deadline when it planned to activate this new policy. Just like Google, Mozilla cited the same rise in HTTPS adoption as the main reason to make the switch to an "HTTP-not-secure-by-default" policy.

Source: Google Chrome to Mark All HTTP Sites "Not Secure" Starting July 2018

 

[Janl1992l]

good move.

 

[Ink]

You can enable this in chrome://flags/#mark-non-secure-as

Chromium Blog post link added to first post.

Related thread: List of interesting experimental flags for Google Chrome

 

[TairikuOkami]

I wonder, what kind of deal did Google make?! Google does not do it for users, but for money, as always. This will only help to spread malware, since SSL was sort of a guarantee, that a webpage is more or less safe (common users are always told that). This will make SSL certificates more accessible to everyone, including malware webpages, not to mention, that when users see, that a webpage is secure, they will automatically assume, that it actually is. So much for theory (it looks good) vs reality.

 

[Azure]

I wonder, what kind of deal did Google make?! Google does not do it for users, but for money, as always. This will only help to spread malware, since SSL was sort of a guarantee, that a webpage is more or less safe (common users are always told that). This will make SSL certificates more accessible to everyone, including malware webpages, not to mention, that when users see, that a webpage is secure, they will automatically assume, that it actually is. So much for theory (it looks good) vs reality.

But google doesn't sell certificates or does it?

 

[TairikuOkami]

But google doesn't sell certificates or does it?

Google is like Umbrella corporation, it deals with biotechnology (Calico), weapons (DARPA) and who knows what else.