News for hackers. Stuff that matters.
Re:Replacing exploit-ridden firmware with a Linux kernel [pdf] by paulmd on Sunday October 29, 2017 @01:34PM (#15580303)
Devil's advocate: if large customers care, AMD can easily give them a "special" microcode image with it disabled. Intel does the same thing with the "High-Assurance Platform" for the intelligence community, which is effectively a ME killswitch.

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.

Re:Replacing exploit-ridden firmware with a Linux kernel [pdf] by bogomipz on Sunday October 29, 2017 @01:44PM (#15580357)
>" Intel does the same thing with the "High-Assurance Platform" for the intelligence community, which is effectively a ME killswitch."

Do you have any links or documentation you could share regarding these exceptions? Thanks.

Re:Replacing exploit-ridden firmware with a Linux kernel [pdf] by GranPC on Sunday October 29, 2017 @02:12PM (#15580480)
Re:Replacing exploit-ridden firmware with a Linux kernel [pdf] by PuffinBlue on Monday October 30, 2017 @06:46AM (#15584101)
To see the Int community have a special mode to disable ME simply confirms that the ME is exploited, if any further proof was needed.
Re:Replacing exploit-ridden firmware with a Linux kernel [pdf] by gmantastic on Sunday October 29, 2017 @02:35PM (#15580602)
This article discusses Intel Management Engine and a company offering laptops with it disabled: https://www.theregister.co.uk/2017/10/21/purism_cleanses_lap...
Re:Replacing exploit-ridden firmware with a Linux kernel [pdf] by Chaebixi on Monday October 30, 2017 @11:21AM (#15585618)
>> Well, some of those privacy and security nerds happen to work for companies like Google and even have influence over those companies' hardware purchases.

>> 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.