3 ms·
The only thing harder than trying to figure out how to execute a side channel attack is attempting to make hardware immune to side channel attacks. And this is
by pixl97 9y ago
The only thing harder than trying to figure out how to execute a side channel attack is attempting to make hardware immune to side channel attacks.
And this is a good question, the Department of Defense and other intelligence agencies have researched attacks like this for decades. Many mainframe/time sharing systems have had much deeper levels of isolation built in because of security requirements of government. It is my personal opinion that Intel especially overstepped their knowledge domain when moving from systems that ran mostly single user 'trusted' code to systems that were multi user and running untrusted code. Processors stopped getting significantly faster and started getting wider (cores). This began the push to commodity virtualization. One processor could run multiple operating systems at once. Again, much like the push disconnected computers with no security to everything being always connected, people wanted to use what they already invested in. If Intel told you that you needed a $10,000 processor and to recompile all your code (hmm, they actually tried that, it sunk like the titanic), you would tell them no. AMD did a much better job at context isolation, but they have always been behind intel in performance, possibly because of this exact issue. With customers not really caring about security and the only attacks were theoretical, things played along just as we see.
So why did this happen?
* Legacy never goes away.
* Performance is king.
* People will go with 'wrong' but cheaper if the problem occurs sometime in the future.
* Marketing departments like graphs with bigger numbers.
* Real isolation is expensive.
* Some people have to be set on fire before they accept they are not fireproof.
- dm319 9y ago> AMD did a much better job at context isolation, but they have always been behind intel in performance, possibly because of this exact issue. Do we need to re-evaluate historical processor metrics? I wonder how Ryzen compares now to equivalent Intel processors. I'm aware that both are vulnerable to Spectre, but it doesn't look like a fix for that is coming any time soon if I have understood things correctly, and it's the lesser of the two evils.