Finding collisions in MD5 and SHA-1 simultaneously is only marginally harder. Using Joux's multicollisions, you can finding a collision in both by running the SHA-1 attack 64 times: this defines 2^64 messages colliding for SHA-1, and you can locate a collision by evaluating all those hashes (wich costs less than finding the SHA-1 collisions with the current attack).

If the issue is with collisions (which is the case in this attack), then you just have to break the innermost hash function. When hashmd5(data1) == hashmd5(data2), you also have hashsha1(hashmd5(data1)) == hashsha1(hashmd5(data2)).

The summary mixes two different issues... SHA-1 is being phased out for certificate signatures, but this is not what the SLOTH attack is about.
SLOTH is about the use of MD5 and SHA1 inside the TLS protocol, to sign or MAC the key-exchange messages.
(Disclaimer: I'm one of the authors of the paper)

I got a Samsung Galay S Relay 4G from T-mobile, and I'm rather happy about it (well, not really from T-mobile, I'm in Europe, so I had to unlock it). It's not the very latest hardware, but it's still decent, and it runs the latest Cyanogenmod.

This all networked car thing is a disaster waiting to happen. The basic idea that your car will make important decisions based on information sent by random strangers can only lead to a catastrophic failure.

What happens when someone sends a signal saying that there is a car stopped just in front of you in the highway? Your own car will stop suddenly, and you might get hurt in the process!

Of course, there will be some kind of authentication of the messages, but everycar has to be trusted by default for the system to be usefull. And we all know how easy it will be to extract the signing key from a given car and to spoof messages...

Apparently, the same bug was in the Linux kernel and has been fixed in 2006, with CVE-2006-0744. So they intially got it wrong, but fixed it before most other OS/hypervisors. It also seems that OpenBSD is not affected.

As far as I'm concerned, I don't give a shit about how much I can do with my phone if it draws too much power. If the battery can not last at least ten hours on idle, a phone is just useless.

A kind of anonymous money could be useful, but I'd rather use one that doesn't double as a pyramid scam.

It's easy to make a bitcoin-clone without this property, you just need to adjust the mining rate so that the early adopters don't get half of the total wealth to ever be available.

Just get a non-x86 machine (e.g. a Raspberry Pi), it will take some time before you can play any commercial games on it...

So after they do their time in the US they're going to be judged in each country where a machine was infected? That's fucking scary!

And if I have a website explaining people how to use TOR, and it turns out that explaining this is illegal in China or in North Korea, will I be extradited to those countries?

Flash support for Linux has always been pretty bad. Most people switched to a 64-bit distro years ago, but Adobe has only supported flash on 64-bits Linux for 6 months... Sure there was a beta version available some time before, but security holes where not fixed in a very timely manner for the beta, so it was mostly useless. In fact things are just going back to normal.

The threat we are currently worried about is not a modern army, it's a bunch of crazy terrorists. They don't need to control the propagation.

Note: I'm not saying that we should be worried about terrorists plots, I'm just saying that, as a society, we are.

That's one of the side effects of the anti-nuclear lobbying. We don't build new reactors, but we still need electricity, so we keep the old ones running longer than they're supposed to...