4 ms·
Summary:. Never consider data in a process to be confidential if you have evil code in the same process (even if it is in a virtual machine or interpreted). I
by londons_explore 8y ago
Summary:. Never consider data in a process to be confidential if you have evil code in the same process (even if it is in a virtual machine or interpreted).
It doesn't actually seem too big a limitation. Apart from JavaScript, EBPF, postscript, etc. there aren't that many places that potentially evil code is run alongside confidential data.
All those now have to be split out into separate worker processes to be secure. The worker processes can have partially shared address spaces through memory mapping, letting the programmer decide what will be shared with the untrusted code.
- anoncake 8y ago> All those now have to be split out into separate worker processes to be secure. How can separate processes help if, as the article says, even virtual machines are problematic? It looks like the only solution is to stop running untrusted code. That includes Javascript.
- londons_explore 8y agoLate follow up here... Virtual machines are affected because the VM kernel is 'running' in the same process as the virtual machine software, and can therefore exfiltrate data.