asus literally gave away who was the one that started the mess
On a side note: The reason this is an uncoordinated mess is that the announcement wasn't supposed to happen for another week. Security researchers figured it out early. The reason they figured it out early is that one of AMD's engineers described the flaw when posting a patch to the Linux kernel. The information in his patch note wasn't supposed to be public. That told everyone where to look. So if you're annoyed by the way this played out, thank AMD.
That's a nice theory but it was discovered by security researchers like in may, disclosed to vendors in june, and the announcement was planned well in advance with proper press release material, whitepapers, and all that other stuff for the meltdown and spectre website.
AMD releasing what it was a week early was pretty minor actually.
Joseph Green
pretty sure no one was ready to deploy their patches yet thats why
Ethan Price
- /* Assume for now that ALL x86 CPUs are insecure */ - setup_force_cpu_bug(X86_BUG_CPU_INSECURE); + if (c->x86_vendor != X86_VENDOR_AMD) + setup_force_cpu_bug(X86_BUG_CPU_INSECURE);
>Assume for now that ALL x86 CPUs are insecure Implying previous comment in the code didn't exist. Oh, you motherfucking retard.
Isaiah Martinez
what's the alternative? not post a patch? not comment the patch and hope nobody figures out the content?
>pretty sure no one was ready to deploy their patches yet thats why
Apple released their OSX kernel patch on the 6th of Dec only the release notes were generic at the time but have been updated recently to describe what the patch did.
Jonathan Long
It's not like people didn't work it out from the fucking X86_CPU_INSERCURE_BUG flag added to the linux kernel in like early december
Matthew Perez
>yes goy divert your attention to amd >don't blame intel oy vey
Robert Reyes
>as if other executives matter
Nathan Flores
>The information in his patch note wasn't supposed to be public. I think he knew very well what he was doing.
Liam Baker
wasn't a tunblr dude sleuthing that did it all? sue you can say that this or that engineer annotation/comment on a public piece of code had the most meat in the bone and ended up verifying it all, but the dude was already looking for something suspicious. He just found that thing that made him finally go, aha. jackpot.
John Price
not to mention this, which is way more inconspicuous than a comment in a obscure piece of code.
Oliver Mitchell
and this, do you really think momma lisa is mad at that engineer? she gave the man a big fat bonus.
Hudson Hill
>insecure yes user, intel is insecure right now. because their chips are all unsecure.
Grayson Williams
Is AMD evil lads? Please tell me, you're the only ones I can trust since everyone is telling lies on the internet.
