5 ms·
The title ought to be updated to specify the container types in question are privileged containers. Even if the original blog post doesn’t. A privileged conta
by oso2k 7y ago
The title ought to be updated to specify the container types in question are privileged containers. Even if the original blog post doesn’t. A privileged container is quite like running a process with a user that has sudo permission. Being surprised that such a container can do bad things seems disingenuous. It’s like saying, “When you give me the keys to your house, I can rob you blind. I just need to figure out which key is for the front door.”
- tptacek 7y agoThe post says, over and over, almost ad nauseam, that you shouldn't be using --privileged and that the original tweet depends on --privileged; moreover, it presents an alternate version of the escape that doesn't depend on --privileged (but does depend on other elevated privileges). The title should not in this case be editorialized; relative to the topic, it's about as boring as titles come.
- lawnchair_larry 7y agoI think the title is a bit clickbaity, perhaps unintentionally. I think parent’s point is that this post isn’t really going to teach you anything at all about docker container escapes, but rather, it teaches you about escaping containers that an admin took several deliberate uncommon and non-default steps to basically escape the container for you. If one clicked it to learn about real world container escapes, they left disappointed.