Microsoft Warns Customers Away From RC4 and SHA-1 92
Trailrunner7 writes "The RC4 and SHA-1 algorithms have taken a lot of hits in recent years, with new attacks popping up on a regular basis. Many security experts and cryptographers have been recommending that vendors begin phasing the two out, and Microsoft on Tuesday said it is now recommending to developers that they deprecate RC4 and stop using the SHA-1 hash algorithm. RC4 is among the older stream cipher suites in use today, and there have been a number of practical attacks against it, including plaintext-recovery attacks. The improvements in computing power have made many of these attacks more feasible for attackers, and so Microsoft is telling developers to drop RC4 from their applications. The company also said that as of January 2016 it will no longer will validate any code signing or root certificate that uses SHA-1."
Re:If SHA-1 is a problem, what does that make MD4? (Score:2, Informative)
Funnier (or sadder) still, NTLM v2 is unsalted rc4.
Re:The time has come the walrus said... (Score:4, Informative)
MD5 is broken, SHA1 has been weakened slightly but it isn't broken.
The term broken is only used when it is trivial to crack and/or forge.
Re:SHA1? insecure? (Score:4, Informative)
Specifically the 2nd SHA family are usually called SHA-224, SHA-256, SHA-384, and SHA-512
Re:The time has come the walrus said... (Score:5, Informative)
In the field of cryptography, the term "broken" is used whenever the work factor to crack is less than that of a brute force attack. Stevens' 2^61 collision attack against SHA1 means that SHA1 is broken.