If you're an ordinary user worried about #meltdown and #spectre exploits: the usual guidelines apply. Update your software and use an ad-blocker. The lessons here important. Performance and security are inevitably in tension, and in my view, it is past time we chose security.
-
-
Also, who named these exploits? The names are


and so correctly evocative of the issues raised by the two different but related structural issues. Spectre haunting all modern chips... The Intel meltdown... Sometimes geek poetry is real poetry. :-DShow this thread -
This is a fairly accessible explanation of
#meltdown by@pwnallthethings. (Yes, it has a tiny bit of code but you can follow along if this stuff interests you).#Spectre is more subtle; will post if I find an accessible explainer. https://medium.com/@pwnallthethings/time-travelling-exploits-with-meltdown-1189548f1e1d …pic.twitter.com/9cRWfPnSVB
Show this thread -
Update, folks. Update your software. Best defense. Lots of people are working hard to rollout
#spectre#meltdown mitigations. (Many updates were out much earlier! But no protection till you update!)https://twitter.com/aprilmpls/status/949053354642235392 …Show this thread -
Just tried to describe
#Spectre to a completely non-technical person, finally ended up saying it’s like, umm, platform 9¾ on King’s Cross. ¯\_(ツ)_/¯pic.twitter.com/czMiMpa23W
Show this thread
End of conversation
New conversation -
-
I've read elsewhere that AMD also has similar problems - all the chipmakers have some form of the problem - Intel is more severe because more users rely on their chipsets.
-
No, Intel is more Severe because they made an architectural choice that favored performance over security where AMD did not. They all have the Spectre issue but Meltdown is all Intel.
End of conversation
New conversation -
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.