2 ms·
> Xen (derived from the original exokernel work) runs AWS on a bazillion servers. So there's an interesting point there: what's the practical difference betwee
by geofft 10y ago
> Xen (derived from the original exokernel work) runs AWS on a bazillion servers.
So there's an interesting point there: what's the practical difference between a microkernel architecture and a microservices architecture?
Local privilege escalation on Linux has been entirely too easy. But privilege escalation on Xen (from one domain to another) has been relatively hard, and AWS works on that assumption. So you treat each Linux image as if it's within one privilege domain, and exploits like the one in this article don't affect you. You can't get from one VM to another, because each VM has its own filesystem server.
The only practical difference, I think, is that microservices exist in the real world, and microkernels have been tried many times and have (with a few exceptions) failed. But the security benefits are about the same.
- nostrademons 10y agoIt's pretty similar from a security standpoint. The point of a microkernel is to get process-isolation guarantees at a much finer-grained level than traditional monolithic kernels allow: not only do you guarantee that processes can't stomp all over each other, but you also guarantee that they can't stomp on kernel data structures like filesystems or drivers. Microservices give this as well, since if there's only one process running on the box, there's not much for it to stomp on (except, well, all the other OS cruft like shells and debugging tools that typically goes on a VM but could be used to turn a pwned box into a spam farm). The big downside of microservices is the complexity they introduce, both in terms of the networking & IPC overhead (which isn't free, and in many cases can consume a majority of the CPU time of the service) and in terms of programming & devops time. Hence some of the interest in unikernels, which both eliminate the other OS cruft that's attackable and eliminate much of the CPU overhead of communicating between microservices. The tooling doesn't really exist for unikernels yet, though - there's no pragmatic, drop-in solution where you can just write a binary and be able to trace & debug performance problems on a production box.