{"id":2183,"date":"2018-03-01T19:06:01","date_gmt":"2018-03-01T23:06:01","guid":{"rendered":"http:\/\/pro-webs.net\/blog\/?p=2183"},"modified":"2018-03-01T19:42:33","modified_gmt":"2018-03-01T23:42:33","slug":"google-dictates-blanket-ssl-for-all","status":"publish","type":"post","link":"https:\/\/pro-webs.net\/blog\/2018\/03\/01\/google-dictates-blanket-ssl-for-all\/","title":{"rendered":"Google Dictates Blanket SSL for All"},"content":{"rendered":"

\"\"So on February 8, 2018, in a very militant move Google announced that “Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as \u201cnot secure<\/strong><\/span>\u201d”.<\/p>\n

Great, so that mom and pop recipe site, or your restaurant’s menu online, or thesaurus.com, or the local youth sports page and more. These small, websites that we use for a variety of reasons, which do not collect money in any form much less credit cards are all going to say “NOT SECURE<\/span><\/strong>” when we visit them.<\/p>\n

Chrome’s new treatment of HTTP pages.<\/strong><\/p>\n

\"\"<\/p>\n

FireFox & current Chrome does this too, but not in your face like Google intends to do.<\/strong><\/p>\n

\"\"<\/p><\/blockquote>\n

Don’t get me wrong, I am all about security, my problem is that people will be scared to visit these types of sites because “it’s not safe”. The language is all wrong…. “Not Secure” & “Connection Not Secure<\/span><\/strong>” are fully inaccurate, especially given the NON-Commerce venue of such websites. The correct terminology would be “Connection not encrypted<\/strong><\/span>“.<\/p>\n

The logic is like this, Google has website pbs.org marked as a safe website via their own transparency report<\/a>, but then at the finish line in the address bar they say it’s not secure. In fact for the purpose of the website and the purpose of the user’s visit, it is secure. It’s just not encrypted and has no reason to be.<\/p>\n

So why don’t website owners just get an SSL? Seems reasonable enough huh?<\/strong><\/span><\/p>\n

Even though there are free SSL certificates, many cannot complete the process on their own and end up paying up to $150 (biggest price tag I’ve seen yet) to someone who can. That’s a yearly price kids! Even if the website owner has the ability to complete the forms and verification, likely they haven’t the knowledge, nor the access to actually install the certificate…. So they still have to pay like $15-$75 a year to have the SSL installed.<\/p>\n

These don’t seem like big expenses, but what about site’s like my dad’s Masonic Lodge<\/a>, this veterans help group Ranger Farms<\/a> or this Youth Football<\/a> website? These non-profit, community not for profit and club type pages don’t have the money. If you go to Google and search you will see thousands and thousands of pages without SSL. So very many of them do not need SSL for any reason. This whole thing makes me wonder if Google bought a certificate authority recently or something =P<\/p>\n

The correct terminology is “Connection not encrypted<\/strong><\/span>“, in fact Google saying someone’s website is secure with one side of their face and then not with the other is ridiculous for such a huge, influential company. I think website owners should sue the browser companies for misrepresenting their interests!<\/p>\n

PS: I borrowed the bully image from http:\/\/www.pbs.org\/<\/a>, seemed appropriate for this situation.<\/p>\n","protected":false},"excerpt":{"rendered":"

The correct terminology is “Connection not encrypted”, in fact Google saying someone’s website is not secure with one side of their face and then not with the other is ridiculous for such a huge, influential company. I think website owners should sue the browser companies for slander!<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[995],"tags":[2632,1113,72,1698,1115],"class_list":["post-2183","post","type-post","status-publish","format-standard","hentry","category-myths-misconceptions","tag-chrome","tag-firefox","tag-google","tag-security","tag-ssl"],"_links":{"self":[{"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/posts\/2183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/comments?post=2183"}],"version-history":[{"count":0,"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/posts\/2183\/revisions"}],"wp:attachment":[{"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/media?parent=2183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/categories?post=2183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pro-webs.net\/blog\/wp-json\/wp\/v2\/tags?post=2183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}