Relevant Items
Refine Search expand_more
Blog add
Solutions add
Products add
Product Categories add
16 Results for 'SHA-1'
Credential Lifecycle Management

Why SHA-1 Migration is Hard, And How to Address the Challenge

Why have so many organizations delayed their SHA-1 migration?  
Digital Certificates

Bye Bye SHA-1

Entrust Datacard Stops Issuing SHA-1 Certificates

SHAttered - First SHA-1 Collision

Google and CWI announced SHAttered, an attack on the SHA-1 cryptographic hash function. The attack was demonstrated by allowing the cryptographic signature on a good PDF to be the same as on a bad PDF. In other words, they forged the signature.

SHA-1 in 2017

 If you have yet to migrate to SHA-2, check out Entrust Datacard’s SHA-2 Migration Guide. It will help you plan and execute a successful SHA-2 migration to avoid extra costs, eliminate service disruptions and ensure compliance.

Building Your Digital DNA: PKI and Cryptographic Disruptors

Researchers have demonstrated several vulnerabilities in MD5. The IETF has prohibited RC4 for use in TLS. More recently, you may have dealt with the impact of SHA-1 being removed as an acceptable algorithm in many standards, including PCI and CAB Forum, according to Entrust Datacard. 

Changes to Support SHA-1 Migration

Entrust provides security beyond the TLS certificate. We are a strong supporter of the CA/Browser Forum standards and also support the requirements provided by our root embedding partners such as Microsoft and Mozilla. 

What's the Future for SHA-1 and Browser Users as of January 1, 2016?

On January 1, 2016, the public trust certification authorities (CAs) will stop issuing SHA-1 signed SSL/TLS certificates. The bottom line is SHA-1 is vulnerable. New studies have shown that the safety factor is decreasing. Continuing to issue SHA-1 signed certificates could compromise a CA or could compromise a legitimate website. Unfortunately for old browser and operating users, the servers must continue to move to SHA-2 signed certificates. These users should try to move to supported systems.

Keep Moving to SHA-2 — Leading Browsers Fast Track SHA-1 Deprecation

Research indicates that SHA-1 signed SSL/TLS certificates face increasing vulnerabilities forcing leading browsers to reconsider how long they will support this technology. This blog outlines dates around the phasing out of SHA-1.

SHA-1 Freestart Collisions

The Freestart collision for full SHA-1 paper was released by Marc Stevens, Pierre Karpman and Thomas Peyrin. This is not a collision attack on the SHA-1 function itself, but on the compression function that underlies it. The research paper states "Freestart collisions, like the one presented here, do not directly imply a collision for SHA-1. However, this work is an important milestone towards an actual SHA-1 collision and it further shows how graphics cards can be used very efficiently for these kind of attacks."

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

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.
Page 1 of 2