Re:NIST Retires SHA-1 Cryptographic Algorithm
by AlotOfReading on Thursday December 15, 2022 @12:40PM
(#34002978)
You shouldn't choose SHA-1, that's the point of this announcement. Seeing it indicates both that there was the potential for malicious input and that the code is old. The appropriate mitigation is to move to a secure hash, not CRCs. You may not know the bounds and distances exactly, but you know them probabilistically. Bit errors almost always map to a different hash.
The same is true of CRCs over a large enough input as an aside. I don't believe exhaustive analysis has been done for most CRCs > 64 bits due to the infeasibility, though you can obviously estimate lower bounds.
The same is true of CRCs over a large enough input as an aside. I don't believe exhaustive analysis has been done for most CRCs > 64 bits due to the infeasibility, though you can obviously estimate lower bounds.