Filter Blogs expand_more
Blog add
Authors add
Markets add
Solutions add
Products add
Product Categories add
23 Results for 'Google'
Blog

By Entrust Datacard

November 30, 2013

On Saturday, Forbes discussed Google’s 2014 vision to make user-generated passwords obsolete. It’s an initiative that deserves praise and is long overdue. Someone is finally taking strong authentication and identity-based security seriously — particularly in the consumer space.
Blog

By Bruce Morton

July 14, 2014

On July 2, Google became aware of fraudulent certificates that were incorrectly issued to Google-owned domain names. The miss-issued certificates could have been used to spoof content, perform phishing attacks or perform man-in-the-middle (MITM) attacks. The following actions were taken to resolve the problem.
Blog

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

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

By Chris Taylor

December 02, 2013

On Saturday, Forbes discussed Google’s 2014 vision to make user-generated passwords obsolete. It’s an initiative that deserves praise and is long overdue. Someone is finally taking strong authentication and identity-based security seriously — particularly in the consumer space. It does, however, come with some caveats.
Blog

By Bruce Morton

March 21, 2016

Entrust Datacard puts Google's cybersecurity safeguards to the test. See if they passed or failed. 
Blog

By Bruce Morton

May 10, 2017

Google just announced they will not be enforcing certificate transparency (CT) logging for all new TLS certificates until April 2018. 
Blog

By Bruce Morton

September 06, 2013

Public Key Pinning was great idea at first. Google used static public keys to protect their websites. In doing so, the keys were embedded in Chrome and were useful in helping users find the DigiNotar attack in 2011, and in a mistaken certification authority (CA) certificate issued by TURKTRUST in 2012.
Blog

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

By Bruce Morton

July 17, 2014

Learn how to gain better Certificate transparency over your domains. Effective December 2014, Entrust will be deploying Certificate Transparency which means that all EV SSL certificates will include the signed certificate timestamp (SCT) and will be logged in a public and all existing non-expired EV SSL certificates will be submitted to Google to be included in a public log. Google has determined there will be no privacy for EV SSL certificates using internal domain names. All certificates will be logged with complete contents.
Page 1 of 3