4 ms·
I don't think the actual technology he was talking about is relevant. The message is that people writing the linux kernel make a lot of mistakes, and it result
by Majestic121 11y ago
I don't think the actual technology he was talking about is relevant.
The message is that people writing the linux kernel make a lot of mistakes, and it result in security holes. Those same people (or the same kind of people) also write X (Docker, x86 virtualization, whatevs...), so mistakes and security holes are to be expected.
I do not necessarily agree with the message, but this is how I understand it.
- geofft 11y agoI understand that message, but it's so little of a message that it doesn't seem useful. Why should we believe that it's equally easy to make mistakes and security holes when writing kernels, OS virtualization, and hardware virtualization? The security models of these things are very different (for instance, a kernel has multiple user accounts, hardware virtualization has just "admin" and "VM"), the underlying designs are very different in complexity, the requirements for legacy compatibility are different, etc. etc. etc.