6 ms·
Is the solution to this and previous side channel bugs to simply not run untrusted and trusted code on the same machine? Basically a revert to the security mod
by alkonaut 8y ago
Is the solution to this and previous side channel bugs to simply not run untrusted and trusted code on the same machine?
Basically a revert to the security model of Windows XP. We should assume access to execute any code means the same security level as having physical access to a machine (I.e. full machine ownership)?
- zik 8y agoNo, as he points out in the article even a kernel call can change the virtual address space so even two threads of the same program may leak data. There's basically no known fix except to disable hyperthreading entirely.
- alkonaut 8y agoYes I meant more generally - effectively: at what point do we trust that there are no side channels in a modern cpu? It seems they are complex enough that the answer may be "never", at least for some high risk scenarios.
- DyslexicAtheist 8y ago> There's basically no known fix except to disable hyperthreading entirely. on kabylake & skylake this has been the recommendation anyway https://lists.debian.org/debian-devel/2017/06/msg00308.html https://lists.debian.org/debian-devel/2017/06/msg00308.html
- tambre 8y agoThat was the recommendation before the microcode fixes for the issue became widely available.
- pas 8y agoIf you pin VMs to different cores, never sharing hyperthreads, then the risk is contained per VM (or per core).
- pabloski 8y agoLet's hope there's no inter-core side-channel lurking in the shadows :( It is time to rethinking the engineering methodologies we use in the electronics/informatics field.
- pocak 8y agoIf you give two threads on one core to one VM, the VM could attack the hypervisor. It could have one thread run the TLB probe loop while the other does something that's handled by the hypervisor.
- AlphaSite 8y agoIsn’t there typically a VMM per VM? So the risk is then lower? http://3.bp.blogspot.com/-OyjQUpLowmg/Udz1_NxqNLI/AAAAAAAABV8/-kBslSjUXUg/s1600/VMM.jpg http://3.bp.blogspot.com/-OyjQUpLowmg/Udz1_NxqNLI/AAAAAAAABV...
- JdeBP 8y agoFor more on which, see the news from a few days ago: * https://www.mail-archive.com/source-changes@openbsd.org/msg99141.html https://www.mail-archive.com/source-changes@openbsd.org/msg9... (https://news.ycombinator.com/item?id=17350278 https://news.ycombinator.com/item?id=17350278)
- pjc50 8y ago> not run untrusted and trusted code on the same machine? That would be an incredible disaster, especially if you count "inside a VM" as "on the same machine". Even more so if you count Javascript as "code". And I think it's an overreaction.
- alkonaut 8y ago> And I think it's an overreaction. I think it is too. Perhaps a better question is: should we really be using the same kind of threat models and mitigation strategies for my gaming machine where I'm alone, and another extreme: A machine running virtual machines for a cloud provider? For the latter case, issuing microcode/OS fixes or recompiling apps to be more secure but losing 10% performance is probably a worthwhile thing. For the single user machine it's absolutely unacceptable. A gamer would much rather have the XP security model than lose 10% performance in even some rare scenarios due to (for example) extra cache flushes designed to mitigate timing attacks! I'd at least want the option. So while I don't think that everything we held to be true about computer security is about to go out the window, I almost hope that the future will hold different security for different scenarios. Just because I run the same OS on the same CPU doesn't mean I necessarily need the same security.
- AstralStorm 8y agoIt is doable if the hardware supports it well. Especially with virtual machines. However it is expensive to implement and thus even high end consumer mainboards have problems today. (try passing through a GPU) And unless you have multiple CPUs or can ensure the cores do not interact in unexpected ways, you essentially have to accept the cost, remain vulnerable (and eat the worms) or replace the hardware with something fixed.
- pjc50 8y ago> A gamer would much rather have the XP security model .. but you probably still don't want your machine to be remotely exploitable by other players. And gaming has the interesting security issue of "anti-cheat", where it's useful if players can prove they're not leaking information from the game process on their own machine. And lots of people will use the same machine to play games and do online banking. Perhaps the way out is more than one "computer" on the same board with different security models. There's already bits of this with TPMs and ILO systems, but the manufacturers care more about keeping them proprietary than making them usable.
- pjmlp 8y agoI think you mean the security model of Windows 9X. XP, specially after SP2 was as safe as NT, if users bother to actually make use of administrator/user separation roles.
- alkonaut 8y agoRight. I forgot XP wasn’t the ancient one.