{"id":11461,"date":"2018-02-13T04:30:10","date_gmt":"2018-02-13T12:30:10","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2018\/02\/13\/news-5232\/"},"modified":"2018-02-13T04:30:10","modified_gmt":"2018-02-13T12:30:10","slug":"news-5232","status":"publish","type":"post","link":"https:\/\/www.palada.net\/index.php\/2018\/02\/13\/news-5232\/","title":{"rendered":"Chrome 68 to condemn all unencrypted sites by summer"},"content":{"rendered":"

<\/p>\n

Credit to Author: Gregg Keizer| Date: Tue, 13 Feb 2018 03:10:00 -0800<\/strong><\/p>\n

Google has put a July deadline on a 2016 promise that its Chrome browser would tag all websites that don’t encrypt their traffic.<\/p>\n

“Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as ‘not secure,'” wrote Emily Schechter, a Chrome security product manager, in a Feb. 8 post<\/a> to a company blog.<\/p>\n

Google has scheduled Chrome 68 to release in Stable form – analogous to production-level quality – during the week of July 22-28.<\/p>\n

Starting then, Chrome will insert a “Not secure” label into the address bar of every website that uses HTTP connections between its servers and users. Sites that instead rely on HTTPS to encrypt the back-and-forth traffic will display their URLs normally in the address bar.<\/p>\n

Google’s campaign to call out HTTP websites as unsafe began in 2014, with the search giant ramping up the effort in September 2016<\/a>, when it told users Chrome 56 would shame pages that didn’t encrypt password or credit card form fields. Chrome 56 debuted in late January 2017, and immediately started to apply the “Not secure” label to pertinent pages.<\/p>\n

The push for always-HTTPS – backed by Google and others, including Mozilla, maker of Firefox – has worked, Schechter argued. Eighty-one of the web’s top 100 sites, she asserted, now used HTTPS by default, while 68% of Chrome traffic on Windows and Android (by pages) and 78% on both macOS and Chrome OS was encrypted. That was up significantly from September 2016, when Schechter said half of all Chrome desktop page loads were being served via HTTPS.<\/p>\n

Eventually, Chrome’s “Not secure” label will be accompanied by a red-for-danger icon.<\/p>\n

At some point, Chrome will not only tell users that a HTTP page is “Not Secure,” but will add a red-for-danger icon to emphasize the point.<\/p>\n

Users can enable Chrome’s new HTTP tagging now by typing chrome:\/\/flags<\/i> in the address bar, then finding the item described as “Mark non-secure origins as non-secure.” Selecting “Enable (mark with a Not Secure warning)” and relaunching Chrome replicates what Chrome 68 will display after Google sets that option as the default. Choosing “Enable (mark as actively dangerous)” displays the red icon as well.<\/p>\n

What Google does – or doesn’t – with Chrome has a huge impact on the web simply because of the browser’s massive influence. In January, for instance, analytics vendor Net Applications pegged Chrome’s user share at 61.4%, making it as dominant as Microsoft’s Internet Explorer was in 2010, when Google’s browser was just two years old.<\/p>\n

That user share has enormous sway over all sites, a club and carrot that Google constantly wields. No site wants to give all those Chrome users the impression that it’s unsafe, and to be avoided. As a result, many sites have fallen in line with Google’s demand that the web go all-in on HTTPS.<\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Gregg Keizer| Date: Tue, 13 Feb 2018 03:10:00 -0800<\/strong><\/p>\n

\n
\n

Google has put a July deadline on a 2016 promise that its Chrome browser would tag all websites that don’t encrypt their traffic.<\/p>\n

“Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as ‘not secure,'” wrote Emily Schechter, a Chrome security product manager, in a Feb. 8 post<\/a> to a company blog.<\/p>\n

Google has scheduled Chrome 68 to release in Stable form – analogous to production-level quality – during the week of July 22-28.<\/p>\n

Starting then, Chrome will insert a “Not secure” label into the address bar of every website that uses HTTP connections between its servers and users. Sites that instead rely on HTTPS to encrypt the back-and-forth traffic will display their URLs normally in the address bar.<\/p>\n

To read this article in full, please click here<\/a><\/p>\n<\/section>\n<\/article>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[11062,10643],"tags":[12014,4314,714],"class_list":["post-11461","post","type-post","status-publish","format-standard","hentry","category-computerworld","category-independent","tag-browsers","tag-internet","tag-security"],"_links":{"self":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/11461","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=11461"}],"version-history":[{"count":0,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/11461\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=11461"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=11461"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=11461"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}