However, these fixes are generally not offered to the public even when they already exist (again, see: Intel HAP).
The rules of the game are different when you're one of the Super 7 instead of just some random pleb. And increasingly those guys are no longer interested in leaving this threat vector open, which says something.
Do you have any links or documentation you could share regarding these exceptions? Thanks.
>> So now AMD has just lost a big chuck of potential Google business...
> Devil's advocate: if large customers care, AMD can easily give them a "special" microcode image with it disabled...
> However, these fixes are generally not offered to the public even when they already exist (again, see: Intel HAP)...
Google could take the "don't be evil" motto one step further: they could require CPU vendor give them publicly available microcode that disables these "features." Basically, they could use their market clout to put the PC market in the right direction.
There's nothing weird in caring about security.
Data in tech companies and banks is worth hundreds of millions. Attackers are therefore willing to pay millions for a ME 0-day.
So now AMD has just lost a big chuck of potential Google business, and who knows what kind of other potential contracts, because it continues to ignore this issue instead of actually showing some leadership on it.
Maybe it's time for AMD to actually differentiate from Intel on this issue?