Home >> Linux >> In Encryption Push, Chrome Flags HTTP Sites as ‘Not Secure’

In Encryption Push, Chrome Flags HTTP Sites as ‘Not Secure’

On Tuesday, Chrome started marking sites that don’t use HTTPS as “not secure.” From a report: First announced two years ago, Google said it would flag any site that still uses unencrypted HTTP to deliver its content in the latest version of Chrome, out Tuesday. It’s part of the company’s years-long effort effort to gradually nudge more webmasters and site owners into adopting HTTPS, a secure encryption standard for data in transit. Any site that doesn’t load with green padlock or a “secure” message in the browser’s address bar will be flagged — and shamed — as insecure. […] According to nightly data compiled by security experts Troy Hunt and Scott Helme, roughly 100 of the top 500 websites are still serving their pages over unencrypted HTTP — all of which will today be flagged as “insecure.” Many of those sites — like Baidu, JD.com, and Google.cn — are Chinese language sites, but many popular Western sites — including BBC.com, DailyMail.co.uk, and Fedex.com — are HTTP. Of the top million sites, a little over half do not redirect to HTTPS. Chrome 68 also brings with it Page Lifecycle API, and the Payment Handler API. From a report: The Payment Handler API builds on the Payment Request API, which helped users check out online. The new API enables web-based payment apps to facilitate payments directly within the Payment Request experience, as seen above. As with every version, Chrome 68 includes an update to the V8 JavaScript engine: version 6.8. It reduces memory consumption as well as includes improvements to array destructuring, Object.assign, and TypedArray.prototype.sort. Check out the full list of changes for more information.


Share on Google+

Read more of this story at Slashdot.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*