4 ms·
Here’s the thing. I read the Meltdown and Spectre papers after getting frustrated with the hand-wavy descriptions people were writing about the vulnerabilities.
by js2 9y ago
Here’s the thing. I read the Meltdown and Spectre papers after getting frustrated with the hand-wavy descriptions people were writing about the vulnerabilities.
I wish I’d just read them in the first place. They aren’t that long and they aren’t that hard to follow. So I recommend developers read the original papers.
That said: after reading the papers trying to explain the issues to someone else will test your own understanding, so I don’t mean to dismiss what you’ve written.
Aside: I find “so you don’t have to” in the title to be a little off putting.
- cmrdporcupine 9y agoI agree, I sat around at work (@Google) for an hour having my brain muddled by 3 or 4 extremely more-intelligent-than-me engineers giving their explanations, and then sat down and read the very clear paper (complete with example C code) and understood it myself in 10 minutes.
- tomcam 9y agoWould you please link to the original paper? Been looking for it myself
- jwilk 9y agohttps://meltdownattack.com/meltdown.pdf https://meltdownattack.com/meltdown.pdf https://spectreattack.com/spectre.pdf https://spectreattack.com/spectre.pdf
- tomcam 9y agoGreat stuff! Thanks
- captn3m0 9y agoHere's the PDF: https://meltdownattack.com/meltdown.pdf https://meltdownattack.com/meltdown.pdf (I found it extremely readable as well, adding a note on the post)