Overview#Cryptographic Collision happens when two distinct pieces of data render the same Hash digest.
Cryptographic Collision, in practice, should never occur for Secure Hash Algorithms.
The attacker could then use this Cryptographic Collision to deceive systems that rely on hashes into accepting a malicious file in place of its benign counterpart.
Here are some numbers that give a sense of how large scale this Computational Hardness Assumption was:
- Nine quintillion (9,223,372,036,854,775,808) SHA-1 computations in total
- 6,500 years of CPU computation to complete the attack first phase
- 110 years of GPU computation to complete the second phase
More Information#There might be more information for this subject on one of the following:
- Certificate Algorithm ID
- Collision Resistance
- Cryptographic Primitive
- SHA-1 Deprecation
- Triple DES