10K views · Jan 16, 2015 · 49:45 · 1 HN recommender · 3 mentions · discussed 2015–2019
Gernot Heiser presents seL4, a microkernel with a mathematical proof connecting security properties to the binary code, and explains what its open-sourcing means for users. It covers its roles as a microkernel, separation kernel and hypervisor.
Why Hacker News points people here: Cited to explain what formal verification of seL4 guarantees, such as ruling out whole classes of bugs like buffer overflows.
“The whole talk is well worth a watch.”HN comment, 2019
“The whole talk is well worth a watch.”
Talk on building actual systems with seL4.
> This is a great view on history of seL4. Is there a list of use cases where seL4 is being used outside academia? "Can you build actual systems with it?" this video The whole talk is well worth a watch.
“it's not possible for this kernel to have a buffer overflow”
seL4 proofs rule out whole classes of memory bugs.
this video The implementation is correct against this abstract specification ... so bug-free, etc. The implications, there's many of them, but just a few obvious ones: it's not possible for this kernel to have a buffer overflow; it cannot - it provably does not use uninitialized variables or dereference null pointers, there's no stack smashing, you can't have code injection, there's no return oriented programming. Any of that stuff is just not possible - provably. So that's nice!
“it says that it's mathematically impossible for seL4 to suffer from things such as buffer overflows”
seL4 verification claims about buffer overflows.
Spent a while on the weekend reading about the seL4 kernel, which uses capability based security and has end to end mathematical proofs of correctness on the compiler and underlying kernel. Its predecessors are used in Apple's A7 and Qualcomm's chips. Watching this video and it says that it's mathematically impossible for seL4 to suffer from things such as buffer overflows. I'm faaaaaar out of my field here... but this sounds as like a far better improvement in security compared to running things in a chroot. Apart from it being really new (there's just a kernel with a C compiler), would this be a good route to head down for improving security? Why aren't we writing a linux port on this? Kernel info here: link
