seL4 Is Free – What Does This Mean For You? on HackerTube: recommended by 1 Hacker News commenter across 1 month, 2015–2019.
talk · intermediate · dated
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.
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.”
3 Hacker News comments link this video. Each one links back to its thread.
> 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.
in “10 Years SeL4: Still the Best, Still Getting Better” · View on HN
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]
in “Manux – A free Linux-compatible OS designed to withstand attacks in userspace” · View on HN
▶ 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!
in “SeL4: OS with formal correctness + security proof” · View on HN