News for hackers. Stuff that matters.
Re:The hijacking flaw that lurked in Intel chips is worse th... by lightedman on Sunday May 07, 2017 @03:22AM (#14284300)
"MD5 is not broken for the usage that you think it's broken for."

Correct; it's broken for everything since we've got the computational power to make it essentially ineffective.

Re:The hijacking flaw that lurked in Intel chips is worse th... by Xylakant on Sunday May 07, 2017 @03:29AM (#14284318)
That's not entirely true. It's broken in the sense that for every hash given we can compute an input that produces this hash. Constructing a useful input (in this case a working exploit) is much less trivial. The complexity depends significantly on what the desired input should look like. It's easier for input that have the property that they can ignore chunks of the input (googles PDF example), but still hard for others.
Re:The hijacking flaw that lurked in Intel chips is worse th... by megadollar on Sunday May 07, 2017 @03:37AM (#14284340)
We cannot produce an input that produces an arbitrary given hash. Here's an easy counterexample: the all-zeroes md5sum. That's an even harder problem than the one I've claimed is entirely not solved.

MD5 is still preimage and second-preimage resistant.