Fuck you @intel, pay me
9
99
3
508
We got a critical hardware level bug affecting two decades of computers on the third day of 2018 I'm scared for the rest of this year.
13
632
30
1,256
Here's a thread of AWS customers saying their CPU went to shit when Amazon quietly patched this out this week forums.aws.amazon.com/thread…
5
194
16
347
Here's AMD claiming it's not affected and Google VERY SPECIFICALLY saying it is. Turns out we're all screwed.
20
251
21
399
More here from Google: security.googleblog.com/2018…
4
70
3
130
Load newest
Replying to @internetofshit
@RottenKaroluz
1
Replying to @Cube_Republic @internetofshit
I mean... with AMD, that seems to be the solution to everything, so they’re already set 😆
1
Replying to @internetofshit
Luckily, all computers of my family have been built around @AMD processors for more than a decade now. But the corporate machines we have been given are a different story.
There is also a microcode update from Intel/AMD/etc.
Replying to @transkatgirl @internetofshit
Yeah they speculate that they can. AMD has gone record saying they can’t.
1
2
Replying to @transkatgirl @internetofshit
Just read up. It’s fx and earlier that have the exploit. Ryzen on doesnt.
1
Replying to @internetofshit @SPQRzilla
And all the cloud services providers began weeping uncontrollably.
1
1
3
Replying to @internetofshit
Ahahaha, as if my Intel processor wasn't already slow enough. Thanks @intel
1
Does this mean there's not a patch for CVE-2017-5753? Tho that also says "during mis-speculation" and I thought AMD was saying they don't do speculation, so I'm kinda confused (not that it matters, got all Intel machines here)
2
Replying to @internetofshit
Bad news: - it's sorta *kinda* patched; only 1 of the 3 is patched, really
2
2
Load more