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.
-
-
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 -
-
-
-
- Show replies
New conversation -
-
-
any bead on papers discussing the adaptation of the infosec community to start branding significant exploits?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The researchers did. The logic behind the names is interesting.http://mashable.com/2018/01/05/meltdown-spectre-names-cpu-bug/ …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
