8 ms·
10 Years SeL4: Still the Best, Still Getting Better
- mmrezaie 7y agoThis is a great view on history of seL4. Is there a list of use cases where seL4 is being used outside academia? Also, I would like to know why Google didn't go for seL4 and instead created Fochsia? I wanted to mention that we wanted to see if we can use L4 for isolating our network filter from Linux kernel (trustability) but instead we opted for bitvisor (much simpler code base but not verified).
- dmitrygr 7y agobecause that would bore the people who are in the fuchsia team purely to not be bored?
- habitue 7y agoMan, this meme that Fuschia is literally a "dont quit please, bored developers" project is huge on HN. It's repeated often like it's common knowledge. Is there any real corroboration for it, or is it just a fun pet theory people like?
- deleted 7y ago[deleted]
- wmf 7y agoThe fact that Fuschia is a large project without any public purpose, roadmap, architecture process, or governance invites these theories. If you want to be so mysterious you can't complain when people speculate.
- carapace 7y ago*Fuchsia
- ryacko 7y agoI strongly suspect that any roadmap would mostly consist of features present in other existing OSes, removing the mystique. It will probably be like any other modern OS, but designed to be a modern OS from the beginning. Which might save Google 0.1% in electricity costs.
- ansible 7y agoFrom what I've seen, I believe that Fuchsia is intended to eventually replace GNU Linux based Android as the mobile platform for Google... eventually. The idea is to have a good platform for VR/AR apps (soft real-time processing / rendering), while providing a system that can be continually upgraded. Unlike the current situation with the Android ecosystem right now, where a newly released product is lucky to get even a few security updates in a year or so, and have effectively had support dropped after that. Compare that to the ChromeOS ecosystem, where Google guarantees 5 years of support from the time the first production on a platform was released.
- mmrezaie 7y agoBored? I don't think they only wanted to reinvent the wheel and I don't think trustability was one of the motivations of their design!
- rodgerd 7y ago> 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?" https://www.youtube.com/watch?v=lRndE7rSXiI&t=22m https://www.youtube.com/watch?v=lRndE7rSXiI&t=22m The whole talk is well worth a watch.
- mmrezaie 7y agoI forgot to mention that I had seen these, but I thought after so many years from L4's release something like isolating firmwares from the OS in our smartphones would have been done. I am not aware of any other capability based and verified micro kernel in level of [se]L4.
- im_down_w_otp 7y agoWe're using seL4 as the basis for one of our products which is focused on characterizing components, systems, and their failure modes. Mostly targeting critical "Cyber-Phyiscal Systems" and "Software-Intensive Systems of Systems". We have a little operating system, or enough of one to facilitate building the rest of our product atop of it, that goes along with seL4. We'd planned to open source parts of it fairly soon, but prioritizing hiring a few more folks (BD, PM, Eng.) has put that effort on-hold temporarily. Building things with seL4 is easy to do wrong, despite being given a variety of very low-level verified primitives to work with. You still need to put it all together just right. CAmkES is supposed to make this easier, but our experience with it wasn't very good, so we took the hard road and created a Rust-based application framework to go over the top of everything.
- mmrezaie 7y ago> seL4 is easy to do wrong This was our main stopper. seL4 would benefit greatly to teach how everything can be fit together, and where everything can be expected to go.
- im_down_w_otp 7y agoWe overcame this with a significant amount of Rust-i-ness and effort in understanding the guts of the kernel and how it implements its assurances. Basically by providing setup, resource management, and communication abstractions that you just can't get wrong because doing something dumb that would be entirely nuts and/or would result in difficult to deal with run-time errors (as the kernel enforces some of its guarantees) ends up being rejected by the compiler ahead of time.
- repolfx 7y agoWhat sort of mistakes were easy to make?
- anp 7y agoWas this work a part of the post's unnamed self-driving car company project?
- mpweiher 7y agoTFA mentions: "Another fork of L4-embedded is what now runs on the Secure Enclave of all Apple iOS devices." All Apple iOS devices is pretty big.
- vilhelm_s 7y agoBut L4-embedded is not seL4. It would be cool to see some large-scale deployment of a formally verified system.
- carapace 7y agoFWIW, OK Labs was acquired by General Dynamics in 2012.
- atombender 7y agoZircon, the Fuchsia kernel, is much bigger than seL4. For example, it provides a process model and syscall interface. But Google may have other reasons to reinvent their kernel (though they're not starting from scratch; Zircon evolved from the Little Kernel by Travis Geiselbrecht). They may have decided that the flexibility of inventing a new microkernel for their exact requirements and moving fast with it would be more productive than reusing an existing one. Building on the careful verification process of seL4 is presumably quite time-consuming, and might get in the way. When NeXT/Apple started using the Mach kernel, it ended up being heavily rewritten to support Apple's requirements, and they never adopted the microkernel design. Google may have seen a seL4 dependency as being a similar kind of burden. seL4 is also GPLv2, I believe. Might also be a blocker for Google.
- loudmax 7y agoWill it be possible to run a web browser on an SeL4 kernel some day, or is that completely beside the point? Obviously, formally verifying a modern web browser with a javascript engine and everything is a whole other undertaking, so I'll leave that aside. But the notion of using a very secure kernel as the base OS is appealing. Even if a hostile site broke out of the web browser, SeL4 should keep it sandboxed. Presumably, SeL4 could enforce isolation between different browser tabs. Is this something we can look forward to in the future, or are the performance expectations of modern javascript heavy web sites out of line with what SeL4 is likely to deliver? Anyway, there are plenty of other applications beside the web, so glad to see that SeL4 is being used in real world deployments.
- wmf 7y agoTechnically, a capability-based desktop OS makes perfect sense. In practice, the microkernel people have been polishing their kernels and about to start on userspace next year... for 30 years. (One exception to this is QNX which was killed off by weird business decisions.)
- pjmlp 7y agoMy Android devices running userspace drivers written in a mix of Java and C++ thanks to Project Treble seem like a step into the right direction. Or the new userspace device driver model introduced by Catalina. As per WWDC, for every new user space driver API, the old kernel one will be automatically marked as legacy and removed after one OS release, with the long term roadmap to replace all the kernel API extensions. Just like Windows 10 increases the amount of sandboxing with each bi-annual release.
- StudentStuff 7y agoUserspace drivers permit upgrading the kernel to a certain point (depending on how kernel APIs change), but your forever trapped with the bugs and vulnerabilities in the userspace blobs. Its a step forward in kernel upgradability, but it also takes the pressure off vendors like Qualcomm and ARM to upstream their patches. I hope the kernel continues making significant changes that break out of tree, proprietary drivers. The harder it is for these players to act in bad faith, the sooner they'll collaborate with the kernel developers and mainline their code.
- elcritch 7y agoAre there any resources for running SeL4 on a raspberry pi or other arm SBC'S? The article mentions hypervisor support, which makes me think it'd be a possible way to run Linux on top of a secure RTOS. Working in the embedded world and I ponder what could be possible with a high security hypervisor.
- im_down_w_otp 7y agoseL4 isn't an RTOS, FWIW. There is hypervisor support, sort of. Insofar as there's enough there to build your own hypervisor (we ended up needing to do something like this), and there's a sample VMM for a very specific host and guest target combination available that's created via CAmkES. Making an seL4-based hypervisor truly cross-architecture capable as well as generalizable for different host and guest target configurations is a non-trivial, painstaking, arduous task. In fact making anything on seL4 truly cross-platform isn't easy. The kernel doesn't provide much in the way of unifying abstractions over the architecture differences. The different architecture details are mostly thrust onto you to figure out what kind of abstractions you want to make. The MCS (mixed criticality support) stuff in seL4 getting mainlined should make it theoretically possible to invent/create a hypervisor that enables you to run MCU oriented RTOSes & applications in an isolated context atop non-HRT hardware. Data61 has mentioned that they're going to take a whack at making some part of an AUTOSAR stack that runs in a context like this, but I have no idea how far along that is. Separately, we're looking at leveraging the same underlying capability for a variety of different adjacent purposes. That said, there are a variety of supported platforms you can already build seL4 for: https://docs.sel4.systems/Hardware/ https://docs.sel4.systems/Hardware/, our experience has been that some work better than others. It's possible to run in QEMU as well to get started.