Off topic, but "any sufficiently advanced incompetence is indistinguishable from malice."

I'm sure it depends on the building. Some friends and I were talking last week about how irritating it is that the "close door" buttons on the elevators in our building do nothing.

From what I've heard, it's a quarter-truth rather than an outright lie. If Alice finds Bob using friend finder, then this message can appear with Bob's name on it. Because there's no way to tell if a friend request came from friend finder, Bob doesn't know that he's "found friends using friend finder".

It was pretty good for cheap scientific computing clusters. But it's being replaced now by tower computers with 4 GPUs.

To be fair, until recently there were more people in Philadelphia than in all of Utah.

A study that shows that many high-profile websites (which follow the previous best practices) are insecure because they don't take this into account, and proposes enhanced defense mechanisms.

If you can repeatedly find security flaws in web best practices, you're welcome to come join the lab. It pays about $15/hr, plus half your health insurance.

Disclaimer: I work with these guys.

In addition to the CPGPU or whatever what they're calling it, Fusion should finally catch up to (and exceed) Intel in terms of niftilicious vector instructions. For example, it should have crypto and binary-polynomial acceleration, bit-fiddling (XOP), FMA and AVX instructions. As an implementor, I'm looking forward to having new toys to play with.

A quarter billion seems pretty reasonable for keeping other companies off their turf.

More people have been to Germany than I have.

Actually, the #1 problem here would be that it would be disgustingly expensive, an ineffective sound barrier and an inefficient energy source.

To start with, lining the highway with any kind of fancy tech would be fabulously expensive. Maybe you could install parabolic concentrators to reduce the cost, but it would still be impractical this side of Dubai.

Second, consider how loud a speaker with a few watts of power, compared to a nearby highway. Truck rumblings will probably hit the wall with something on the order of a few watts per square meter, tops.

Third, if this is 18% efficient, that's not even 1 dB down.

Hydrogen isn't nearly as dangerous as people think. It doesn't have a very high energy density, and it rises as it burns. In the Hindenberg disaster, an airship with 200,000 m^3 of hydrogen caught fire while still in the air, then crashed into the ground, and almost 2/3 of the passengers and crew survived. I'm pretty sure a car colliding with this barrier would be less spectacular.

I want to see this happen, as do several of my colleagues in the security industry. Unfortunately, this sort of strategy breaks legacy applications so corporations are not going to adopt it.

Pretty much, yeah. The fuel burns rapidly, and its heat increases the pressure in the cylinder. The more heat, the more pressure. Obviously, adding the heat earlier could cause some problems: it could result in less fuel and air in the cylinder (higher initial pressure), or it could damage components, or it could leak heat out, or it could cause the cylinder to fire at an inconvenient time, or whatever. But in principle, it doesn't have to be a problem.

OK, so maybe yogurt is a better example.

It shouldn't really matter that much so long as most of the heat stays in the fuel.

And for your information, honey is delicious and pre-eaten.

Latency 15 cycles, throughput 10 cycles. That's a shame. Also, AESENC has thoughput 2 cycles/round, only half as fast as I expected.

I overstated the case. CBC mode isn't terrible, it's just not the best mode out there.

The main problem with CBC mode is that it isn't parallel. This means that most of the new, faster, timing-attack-resistant libraries can't handle it efficiently (the one I wrote is an exception, but it only works on recent Intel procs and it's ~10% slower than Kasper-Schwabe for bulk encryption). It also means that CBC is a factor of 3 slower on Westmere, maybe 1.5 on VIA chips and 1.5 on the PowerPC G4. Due to optimizations, CBC mode is an additional 15-20% slower than CTR mode in most software libraries. It also has a larger attack surface than CTR mode, and unlike CTR mode it requires decryption.

OCB and GCM modes are really nice because of the integrated MAC. Too bad OCB is patented... if you fit the constraints, there really isn't a better mode for AES.