3 ms·
I spent some time studying this kernel in a graduate class a year or two ago. Basically the kernel was implemented in subsets of C and subsets of Haskell, and
by pnathan 16y ago
I spent some time studying this kernel in a graduate class a year or two ago.
Basically the kernel was implemented in subsets of C and subsets of Haskell, and a 1:1 mapping between C and Haskell was proved. The Haskell code was formally proved to match certain properties in the prover.
One of the key innovations in the seL4 project is a formal treatment of properties regarding memory allocation and usage. That is to say, they were able to write proofs about malloc using only static analysis (just looking at the code, not running it), which was something that's been pretty out-of-reach to that point. Of course, there are limitations to the C code.
So, the seL4 microkernel is provably immune to certain classes of bugs. That's basically the big deal.
If I was looking for a secure kernel, seL4 would be a good starting point to look at, IMO.