Welp: https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/
> A fundamental design flaw in Intel's processor chips has forced a significant redesign of the Linux and Windows kernels to defang the chip-level security bug.
> Crucially, these updates to both Linux and Windows will incur a performance hit on Intel products. The effects are still being benchmarked, however we're looking at a ballpark figure of five to 30 per cent slow down.
> A spokesperson for Intel was not available for comment
Weren't they now.
@rysiek Good lord. That and Management Extensions.
But it's funny how the cloud systems are scrambling to fix this when the owner of the cloud can still read everyone's kernel RAM. Somehow THAT huge security hole doesn't worry the cloud owners.
@natecull they are the ones who can read RAM so why do they care?
They do care about cloud users being able to read kernel mem though, for obvious reasons.
@Wolf480pl @rysiek There ARE claimed ways (from the chipmakers, eg Intel) of putting 'secure enclaves' into the chips such that the owners of the hardware CAN'T access RAM, even in Ring 0 or -1 or whatever hypervisors / Intel ME gives access to.
But, um. One, how much do we trust the chipmakers? And two, how do we get encrypted data into and out of this 'secure RAM' through insecure RAM?
It's maybe possible, but it seems really awkward, and still a big trust point being the chip makers.
