Allow me to summarize x86 side channel attacks: Spectre v1: speculation is insecure by design Spectre v2: secure branch prediction matters Meltdown: Intel are dumbasses L1TF: Intel are monumental, inexcusable dumbasses PortSmash: hyperthreading is insecure by design
-
Show this thread
-
And yes, Spectre v1 and PortSmash aren't going away. Anyone who knows anything about CPUs knew PortSmash was theoretically possible for years (just someone bothered to finally implement it). Disable HT or petition OSes to do security-domain-aware HT by default.
3 replies 24 retweets 109 likesShow this thread -
Also PortSmash should be adaptable to AMD systems with HT (i.e. Zen) and also all the POWER stuff. And it gets worse, because under more specific circumstances and with cleverer exploits, the side channels go beyond HT and to shared caches too.
7 replies 17 retweets 87 likesShow this thread -
Ultimately, computing needs to come to terms with the fact that any time there is *any* shared resource, that's ripe for side channels. This includes main memory and peripheral devices. It's worse and more insidious the lower level and more tightly coupled you make it, like HT.
6 replies 52 retweets 182 likesShow this thread -
This Tweet is unavailable.
-
I have no idea what this "walled garden" you speak of is. You can experiment all you want at home. If you're #46 on the Fortune 500 list you do not get to "experiment, make mistakes, and make
#insecure things" that you then sell to customers.0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Just because companies get to do awful things doesn't mean they should. If you don't care about security, that's great. Feel free to post your password on Twitter. Most of the rest of the world cares.
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
That was also an era where software was a couple of orders of magnitude smaller, where bad actors were few and far in between, and when our lives and livelihoods weren't so utterly dependant on our computers. Times change, and reasonable standards for security change.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.