6 ms·
Getting tired of this shit. "Secure", as a word, does not make things secure. "Container", as a word, also does not make things secure. Sandboxes come in two
by BuuQu9hu 9y ago
Getting tired of this shit.
"Secure", as a word, does not make things secure. "Container", as a word, also does not make things secure.
Sandboxes come in two flavors: Correct by construction, and exploitable. Which flavor is this system?
What makes this better than NixOS? Than Genode? Than Qubes? Where is the actual security writeup? Where's the explanation of the security model for the system? How would I write code which takes advantage of structural security in the system?
Edit: There's a writeup here: https://github.com/linuxkit/linuxkit/blob/master/docs/security.md https://github.com/linuxkit/linuxkit/blob/master/docs/securi... And the Mirage design is here: https://github.com/linuxkit/linuxkit/blob/master/projects/miragesdk/roadmap.md https://github.com/linuxkit/linuxkit/blob/master/projects/mi...
In short, to answer my earlier questions, the sandboxing is undocumented, comparisons to other security-oriented setups are omitted, the limit of structural security is OCaml's type system... This seems like an interesting effort but I am disappointed that it seems more like lip service than an attempt to actually improve on the state of security design.