Fuck you @intel, pay me
9
99
3
509
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,252
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
131
Load newest
True, and I see the only patches for that one are per-application and not really much AMD themselves can do anything about.
Replying to @awnumar @internetofshit
What why? So EVERYONE is getting a shit tier computer?
Replying to @internetofshit
Industry braces for critical Intel security flaw impacting a decade's worth of chips cyberscoop.com/intel-chip-fl…
Replying to @internetofshit
You can avoid the patch... on linux at least. On windows 10... oh right, ya, you're fucked.
Incorrect to some degree. On linux, they enabled or created a feature to deal with the problem but this patch for Intel's fuck up, causes a less than 50% decrease in AMD performance on syntheitic. You can turn the feature off. Haven't heard anything on Windows front.
Funny enough, still getting updates for my.... 3,4 maybe 5 yearold board. Hmmm... ya i think it's only 3 years old.
Replying to @internetofshit
bad news... its still better than AMD lol
Replying to @Exentiostep @internetofshit
Of course I never made that VM passthrough neither I used those PCIe lanes
Replying to @internetofshit
So we're uh. Sorta fucked
Replying to @internetofshit
You can safely avoid the patch if you're running on your own, non-shared hardware and don't rely on virtualization for isolating your security domains, or am I mistaken?
Load more