Or to elaborate further: TO EXPLOIT MELTDOWN YOU NEED SOME JAVASCRIPT ON A WEBSITE. TO EXPLOIT THIS FIRMWARE STUFF YOU NEED KERNEL MODE CODE EXECUTION. LEARN THE FUCKING DIFFERENCE.
Show this thread
Okay, I should've shouted this earlier. THE AMD VULNERABILITIES THAT JUST CAME OUT HAVE NOTHING WHATSO-FUCKING-EVER TO DO WITH MELTDOWN/SPECTRE IN SCOPE, DANGER, OR APPLICABILITY. ANY COMPARISONS DEMONSTRATE A COMPLETE LACK OF UNDERSTANDING AND A FAILURE AT TECH JOURNALISM.
-
-
-
Car analogy for those who still don't get it: HACKERS CAN TAKE OVER YOUR CAR FROM THE OTHER SIDE OF THE COUNTRY vs HACKERS CAN TAKE OVER YOUR CAR BY OPENING THE HOOD AND PLUGGING IN STRAIGHT INTO THE ECU.
Show this thread
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
Where's the claim that there was custom signed code? It sounded like the secure processor driver is stock AMD
- Show replies
-
-
-
Meh... It's just a backdoor in your CPU xD
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Pero eso es el periodismo en todos los campos hoy en día...no hay contraste de información. Solamente importa la atención del público
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
They're not Spectre/Meltdown bad, but they're still bad. Defeats the purpose of Secure Boot, for a start.
-
You mean like the other over 9000 ways you can break secure boot on x86?
- Show replies
New conversation -
-
-
This Tweet is unavailable.
-
Yeah I can always count on
@marcan42 to provide a voice of reason amongst all the chaos and general bullshittery in this industry. haha XD His work (and others in@fail0verflow) have been some of the greatest influences in my life. Makes me strive to be a better person. :)
End of 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.