5 ms·
>Recent reports that these exploits are caused by a “bug” or a “flaw” and are unique to Intel products are incorrect. From the English, this report makes it se
by rhema 9y ago
>Recent reports that these exploits are caused by a “bug” or a “flaw” and are unique to Intel products are incorrect.
From the English, this report makes it seems like there was no bug and no flaw. However, they say that ((bug || flaw) && only_intel) is false, but I have seen that AMD was not impacted.
Seems like this is a bug or flaw, since they are addressing it soon. They make it seem like everyone should be working in the same boat to address this, but they are just trying to un-distance themselves from their competition.
- bonzini 9y ago> since they are addressing it soon. They make it seem like everyone should be working in the same boat to address this I can assure you that indeed "everyone is working in the same boat to address this", and has been doing so for months, across multiple OS and processor vendors. It's already public that Microsoft and Apple have also implemented page table isolation, and certainly Intel didn't name-drop AMD and ARM carelessly in the press release.
- lettergram 9y ago> and certainly Intel didn't name-drop AMD and ARM carelessly in the press release. I'm sure it wasn't careless, but they are (from all accounts I have read) blatantly lying. Intel isn't known for above board practices. They will do what it takes to win - period. Name dropping their competitors (to me), honestly shows me how dire of a situation this is. If it wasn't, they wouldn't feel the need to defend themselves and say, "well look at everyone else".
- kunday 9y agoAccording to project zero report, a lot more than intel CPU's are affected by this issue. See relavant HN post here "These vulnerabilities affect many CPUs, including those from AMD, ARM, and Intel, as well as the devices and operating systems running them." https://news.ycombinator.com/item?id=16065845 https://news.ycombinator.com/item?id=16065845