<story><title>Introducing rkt’s ability to detect privilege escalation attacks on containers</title><url>https://coreos.com/blog/rkt-detect-privilege-escalation.html</url></story><parent_chain></parent_chain><comment><author>catern</author><text>I don&amp;#x27;t have the inclination to write a long comment about this. But reading sections like this:&lt;p&gt;&amp;gt;This state can then be verified whenever a process performs an action requiring a permissions check. For example, when a process requests that a file be opened, the kernel now calls out to the hypervisor. The hypervisor is then able to examine the process state and ensure that it remains consistent with its internal representation of process state.&lt;p&gt;Makes me very uneasy. You&amp;#x27;re making the hypervisor more complicated, duplicating the logic in the kernel, because you feel the kernel is insecure. The only argument for doing this, AFAIK, is that the hypervisor is still simpler overall, and therefore more secure. But when you start introducing these kind of complications, that argument becomes kind of farcical... Adding another layer on top of the kernel and duplicating your permissions checks in there, I do not think that will end well.</text></comment>
<story><title>Introducing rkt’s ability to detect privilege escalation attacks on containers</title><url>https://coreos.com/blog/rkt-detect-privilege-escalation.html</url></story><parent_chain></parent_chain><comment><author>buckhx</author><text>Who is using rkt in production? I&amp;#x27;m working on a system from scratch and planning on using k8s and just assumed docker would be the container engine of choice, but the more I hear&amp;#x2F; read about rkt the more it seems like the better choice.</text></comment>