{"id":4952,"date":"2018-02-10T02:08:35","date_gmt":"2018-02-09T18:08:35","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=4952"},"modified":"2018-02-10T02:08:47","modified_gmt":"2018-02-09T18:08:47","slug":"google-chrome-marking-non-https-sites-insecure-july-2018","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2018\/02\/google-chrome-marking-non-https-sites-insecure-july-2018\/","title":{"rendered":"Google Chrome Marking ALL Non-HTTPS Sites Insecure July 2018"},"content":{"rendered":"<p>Google is ramping up its campaign against HTTP only sites and is going to mark ALL Non-HTTPS sites insecure in July 2018 with the release of Chrome 68. It&#8217;s a pretty strong move, but Google and the Internet, in general, has been moving in this direction for a while.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.darknet.org.uk\/wp-content\/uploads\/2018\/02\/Google-Chrome-Marking-ALL-Non-HTTPS-Sites-Insecure-July-2018-640x395.png\" alt=\"Google Chrome Marking ALL Non-HTTPS Sites Insecure July 2018\" width=\"640\" height=\"395\" class=\"aligncenter size-medium wp-image-4953\" srcset=\"https:\/\/www.darknet.org.uk\/wp-content\/uploads\/2018\/02\/Google-Chrome-Marking-ALL-Non-HTTPS-Sites-Insecure-July-2018-640x395.png 640w, https:\/\/www.darknet.org.uk\/wp-content\/uploads\/2018\/02\/Google-Chrome-Marking-ALL-Non-HTTPS-Sites-Insecure-July-2018.png 648w\" sizes=\"(max-width: 640px) 100vw, 640px\" \/><\/p>\n<script async src=\"https:\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-3033787195489589\"\r\n     crossorigin=\"anonymous\"><\/script>\r\n<!-- Darknet Responsive Post Ad Links [previously link ad unit] -->\r\n<ins class=\"adsbygoogle\"\r\n     style=\"display:block\"\r\n     data-ad-client=\"ca-pub-3033787195489589\"\r\n     data-ad-slot=\"5456620019\"\r\n     data-ad-format=\"auto\"><\/ins>\r\n<script>\r\n     (adsbygoogle = window.adsbygoogle || []).push({});\r\n<\/script>\n<p>It started with suggestions, then forced SSL on all sites behind logins, then mixed-content warnings, then showing HTTP sites are not-secured and now it&#8217;s going to be outright marked as insecure.<\/p>\n<blockquote><p>Three years ago, Google&#8217;s search engine began favouring in its results websites that use encrypted HTTPS connections.<\/p>\n<p>Sites that secure their content get a boost over websites that used plain-old boring insecure HTTP. In a &#8220;carrot and stick&#8221; model, that&#8217;s the carrot: rewarding security with greater search visibility.<\/p>\n<p>Later this year comes the stick. This summer, Google will mark non-HTTPS websites as insecure in its Chrome browser, fulfilling a plan rolled out in September 2016.<\/p>\n<p>Starting with Chrome 68, due to hit the stable distribution channel on July 2018, visiting a website using an HTTP connection will prompt the message &#8220;Not secure&#8221; in the browser&#8217;s omnibox \u2013 the display and input field that accepts both URLs and search queries.<\/p>\n<p>&#8220;Chrome&#8217;s new interface will help users understand that all HTTP sites are not secure, and continue to move the web toward a secure HTTPS web by default,&#8221; <\/p><\/blockquote>\n<script async src=\"https:\/\/pagead2.googlesyndication.com\/pagead\/js\/adsbygoogle.js?client=ca-pub-3033787195489589\"\r\n     crossorigin=\"anonymous\"><\/script>\r\n<!-- Darknet Responsive Post Ad Links [previously link ad unit] -->\r\n<ins class=\"adsbygoogle\"\r\n     style=\"display:block\"\r\n     data-ad-client=\"ca-pub-3033787195489589\"\r\n     data-ad-slot=\"5456620019\"\r\n     data-ad-format=\"auto\"><\/ins>\r\n<script>\r\n     (adsbygoogle = window.adsbygoogle || []).push({});\r\n<\/script>\n<p>I&#8217;m glad I updated this site to SSL before it became absolutely critical, and to be honest with Google Cloud, Amazon AWS and Lets Encrypt offering SSL termination for free, there&#8217;s no real excuse not to be on SSL anymore.<\/p>\n<p>&#8211; <a href=\"https:\/\/cloudplatform.googleblog.com\/2017\/09\/introducing-managed-SSL-for-Google-App-Engine.html\">Introducing managed SSL for Google App Engine<\/a><br \/>\n&#8211; <a href=\"https:\/\/aws.amazon.com\/blogs\/aws\/new-aws-certificate-manager-deploy-ssltls-based-apps-on-aws\/\">New \u2013 AWS Certificate Manager \u2013 Deploy SSL\/TLS-Based Apps on AWS<\/a><br \/>\n&#8211; <a href=\"https:\/\/letsencrypt.org\/getting-started\/\">Getting Started &#8211; Let&#8217;s Encrypt &#8211; Free SSL\/TLS Certificates<\/a><\/p>\n<blockquote><p>Because Chrome holds something like 56 percent of the global browser market share across mobile and desktop platforms, Google&#8217;s name-and-shame label is likely to be noticed by a great many Chrome users and by any websites those fans no longer visit due to security concerns.<\/p>\n<p>While many websites will be affected, plenty are already in compliance. According to Google, 81 of the top 100 websites use HTTPS by default, over 68 percent of Chrome traffic on Android and Windows occurs over HTTPS, and over 78 percent of Chrome traffic on Chrome OS and macOS and iOS travels securely.<\/p>\n<p>Google offers a free security auditing tool called Lighthouse that can help developers identify which website resources still load using insecure HTTP.<\/p>\n<p>The Chocolate Factory&#8217;s shunning scheme follows a similar tack the company has taken to issue warnings to websites that rely on dodgy Symantec digital certificates. <\/p><\/blockquote>\n<p>I would imagine similar standards are going to be pushed out across the other browsers given the time and the fact Google is still the biggest search engine, they define how the web reacts.<\/p>\n<p>Make sure your SSL install is secure using these:<\/p>\n<p>&#8211; <a href=\"https:\/\/www.darknet.org.uk\/2012\/12\/tlssled-v1-2-evaluate-the-security-of-a-arget-ssltls-https-web-server-implementation\/\">TLSSLed v1.2 \u2013 Evaluate The Security Of A Target SSL Or TLS (HTTPS) Web Server Implementation<\/a><br \/>\n&#8211; <a href=\"https:\/\/www.darknet.org.uk\/2016\/12\/sslscan-detect-ssl-versions-cipher-suites-including-tls\/\">sslscan Download \u2013 Detect SSL Versions &#038; Cipher Suites (Including TLS)<\/a><\/p>\n<p>The official blog by Google on this is here:<\/p>\n<p><a href=\"https:\/\/security.googleblog.com\/2018\/02\/a-secure-web-is-here-to-stay.html\">A secure web is here to stay<\/a><\/p>\n<p>I personally think this is a step in the right direction and wonder why only 81 of the top 100 sites are on SSL.<\/p>\n<p>Source: <a href=\"http:\/\/www.theregister.co.uk\/2018\/02\/08\/google_chrome_http_shame\/\">The Register<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google is ramping up its campaign against HTTP only sites and is going to mark ALL Non-HTTPS sites insecure in July 2018 with the release of Chrome 68. It&#8217;s a pretty strong move, but Google and the Internet, in general, has been moving in this direction for a while. It started with suggestions, then forced [&hellip;]<\/p>\n","protected":false},"author":25,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"Google is ramping up its campaign against HTTP only sites and is going to mark ALL Non-HTTPS sites insecure in July 2018 with the release of Chrome 68.","_seopress_robots_index":"","_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[12],"tags":[10668,190],"featured_image_src":null,"featured_image_src_square":null,"author_info":{"display_name":"Darknet","author_link":"https:\/\/www.darknet.org.uk\/author\/darknet\/"},"_links":{"self":[{"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/posts\/4952"}],"collection":[{"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/comments?post=4952"}],"version-history":[{"count":0,"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/posts\/4952\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/media?parent=4952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/categories?post=4952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.darknet.org.uk\/wp-json\/wp\/v2\/tags?post=4952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}