The academics call them Meltdown/Spectre, Google calls them Variant 1-3 (each with a CVE), and there's no good matrix of what bug affects what (which CPUs, kernel leaks, same-context leaks, cross-process leaks, etc).
Show this thread
I'm just going to point out that the people involved in coordinating disclosure on Meltdown/Spectre have done a terrible job of agreeing on names/categories for the various bugs and CPU impact. Even post-disclosure there's still a mess of speculation on what bug affects what CPUs
-
-
-
The Spectre paper claims ARM is impacted but gives zero details beyond "initial testing has confirmed that ARM processors are impacted as well". WTF does that even mean? Which processors and which exploit scenario?
Show this thread -
Hyperthreading is also very important for these attacks due to sharing execution resources, and yet it isn't being mentioned enough.
Show this thread
End of conversation
New conversation -
-
-
Do you think they planned a later release but the community mostly figured it out, so they decided to disclose now?
-
The release was planned for next week, but there's no indication that this would've been done better by then.
End of conversation
New conversation -
-
-
well, the plan was to coordinate it on 9th; google even apologized on lklm for the messy and confusing disclosure that happened yesterday/today
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I have their docs. Site is just slow.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Hey, just call it all a "computerbomb" like the "weatherbomb", then everyone'll agree.
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.