- Colin Percival: Some thoughts on Spectre and Meltdown
While I have not been involved with handling these issues directly, I think it’s time for me to step up and provide both a wider context and a more broadly understandable explanation.
- How Meltdown and Spectre Were Independently Discovered By Four Research Teams At Once | WIRED
“As far as I can tell it’s a crazy coincidence,” says Paul Kocher, a well-known security researcher and one of the two people who independently reported the distinct but related Spectre attack to chipmakers. “The two threads have no commonality,” he adds. “There’s no reason someone couldn’t have found this years ago instead of today.”
- Myths Programmers Believe about CPU Caches – Software the Hard way
Such misconceptions are mostly harmless (and maybe even helpful), but can also lead to bad design decisions. For instance, developers can start to believe that they are insulated from the above concurrency bugs, when working with single-core-systems.
- Why Raspberry Pi isn’t vulnerable to Spectre or Meltdown
Happily, the Raspberry Pi isn’t susceptible to these vulnerabilities, because of the particular ARM cores that we use. To help us understand why, here’s a little primer on some concepts in modern processor design.
- Jens Neuhalfen: Meltdown and spectre explained — for normal people
This is for “normal people”. With these slides I fill the hole between we are going to die! and white noise. You, the reader, will understand what went wrong, how it went wrong, and why this is bad. I will try to minimise the computer specialists words to an absolute minimum. Promised!
(Recording from FrOSCon2018)
- Jon Masters: The spectre of hardware bugs
Great Keynote and detailed slides with more information. (Recording from FrOSCon2018)
This entry was posted on Monday, October 22nd, 2018 at 14:34 and is filed under english, Links.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.