You are not signed on; if you are a visitor please register for a free account!
|The Market Ticker Single Post Display (Show in context)||
User: Not logged on
|User Info||It's Operating As Designed (ROFL!); entered at 2018-01-04 01:14:37|
This all comes from here: https://meltdownattack.com/|
(All exploits must have catchy names now, so we have Meltdown and Spectre).
"Meltdown allows an unprivileged process to read data mapped in the kernel address space, including the entire physical memory on Linux and OS X, and a large fraction of the physical memory on Windows. This may include physical memory of other processes, the kernel, and in case of kernel-sharing sandbox solutions (e.g., Docker, LXC) or Xen in paravirtualization mode, memory of the kernel (or hypervisor), and other co-located instances"
Basically, both of these are cache poisoning attacks combined with an optimisation that should be transparent but isn't quite.
The /correct/ solution is for the silicon to return the /entire/ CPU to the state it was in before whatever speculative action took place, i.e. as if the optimisation had never happened, but whether that's at all practical I'll leave for someone with actual hardware knowledge.