Filter Blogs expand_more
Blog add
Authors add
Markets add
Solutions add
Product Categories add
19 Results for 'Chrome'
Blog

Chrome to Show HTTP Sites as Not Secure

By Bruce Morton
September 09, 2016
Google will soon be issuing a stronger warning to visitors who navigate to a website that does not have the protection of an SSL/TLS certificate. With the release of Chrome 53 on Windows, Google has changed the trust indications to introduce the circle-i. 
Blog

Trust Indication Change in Google Chrome

By Bruce Morton
August 31, 2016
Google is making security icon changes in the Chrome status bar. The changes are based on a research paper prepared by members of Google and University of California, Berkeley. The research evaluated forty icons, seven complementary strings and surveyed 1,329 people. 
Blog

Chrome Will Show Not Secure for all HTTP Sites Starting July 2018

By Bruce Morton
March 09, 2018
In Chrome 68, which will be released in July 2018, we can expect "Not secure" to be provided for all HTTP pages.
Blog

Chrome Shows SSL Warning for Non-FQDNs

By Bruce Morton
October 17, 2013
Entrust completed an internal test recently and was surprised by a warning from Google Chrome version 30. The test case has a Web server with a non-fully registered domain name (non-FQDN) and an SSL certificate from a publicly trusted certification authority (CA).
Blog

Update – Chrome 41 Release and SHA-1

By Bruce Morton
January 27, 2015
When Google Chrome 41 is released, it will treat certificate chains using SHA-1 which are valid past January 1, 2017 as affirmatively insecure.
Blog

SHA-1 Deprecation Update – Not Chrome 41, but Chrome 42

By Bruce Morton
March 13, 2015
Chrome 41 was released on March 3, 2015. You may have noticed, Chrome 41 did not have a change to treat certificate chains using SHA-1 valid past January 1, 2017 to be affirmatively insecure.
Blog

Google is Sun-Setting SHA-1 in Upcoming Chrome Releases

By Bruce Morton
September 10, 2014
Entrust Datacard shares announcement from Google on September 5, 2014, that Chrome will sunset SHA-1 by providing security warnings through the popular browser. SHA-1 is a secure hash algorithm used when signing SSL certificates. SHA-1 provides a unique 160-bit hash value representing the certificate. The hash value is designed so it cannot be the same for two different certificates.
Blog

Chrome Kills Mixed Content for HTTPS

By Bruce Morton
November 20, 2019
In order to provide browser users with the best experience on your website and offer greater security, website owners are encouraged to secure all content including visual and multimedia and ensure that all content comes from secure sources.
Blog

Let’s Test Google Chrome’s Security Overview

By Bruce Morton
March 21, 2016
Entrust Datacard puts Google's cybersecurity safeguards to the test. See if they passed or failed. 
Blog

Certificate Transparency Deployment in 2017

By Bruce Morton
November 14, 2016
Google announced the requirement for Certificate Transparency for all new SSL/TLS certificates in October 2017. This requirement means that Chrome will no longer trust new SSL/TLS certificates that are not qualified for Certificate Transparency (CT). 
Page 1 of 2