GrapheneOS says Linux was built to reject robust architecture and is riddled with holes

Linux was created as a rejection of robust software architecture and tools

GrapheneOS argues that Linux was created as a rejection of robust software architecture and tools: a monolithic kernel with no internal isolation, written in memory-unsafe code, where a typo in an obscure driver for unused functionality can yield fully privileged code execution. The project says the kernel is unstable, unreliable, and insecure, with no clear path to being fixed — and that LLMs, not security researchers, finally made the scale of the problem visible.

A typo in an obscure driver for unused functionality can easily create a fully privileged code execution vulnerability.
  1. somat

    Unix itself was created as a rejection of robust software architecture and tools.

    "I remarked to Dennis that easily half the code I was writing in Multics was error recovery code. He said, "We left all that stuff out of Unix. If there's an error, we have this routine called panic, and when it is called, the machine crashes, and you holler down the hall, 'Hey, reboot it.'"

    -- Tom Van Vleck

    Not that this is a bad thing, but unix was created as a hacker's toy, a small elegant system to play games on, This is why it is so fun to use. I mean, it is not really small or elegant anymore. but that is how it started, not as a robust correct business system. That is also why it got so popular. "A small hackable lowcost operating system with full source" colleges: yes please, and at a critical time in computing history, a very influential generation of hackers learned on it. Something now is better than perfect that does not exist, or that old cliche, worse is better.

  2. qalmakka

    A great pragmatical axiom of security is that if it doesn't come cheap in terms of speed and convenience, it's likely going to fail in the end. People will always pick practicality over security in the real world: if it takes too much time to lock and unlock the front door, the average person will just leave it ajar.

    Linux was a monolithic kernel because in 1991 microkernel were in earnest 25 years too early. Computers didn't really have the extra performance to spend for things like IPC and stuff. lots of other kernel designs that started back then like NT and Nextstep (was the NextStep kernel called XNU already? I guess not) all tried the microkernel route and then ended up doing stuff like networking at kernel level anyway because it just didn't work well enough.

    arguably nowadays we have extra headroom to spare so stuff like containers, sandboxing, userspace drivers are becoming more and more commonplace.

  3. 7373737373

    That most of the Linux kernel runs in https://en.wikipedia.org/wiki/Protection_ring 0 should have stopped decades ago

    Perhaps processor architectures like the https://en.wikipedia.org/wiki/Intel_iAPX_432 which do away with such coarse grained and therefore dangerous abstractions by using capability-based addressing should have succeeded earlier too. This is how modern programming languages should be structured too, instead of giving no guarantees to programmers (and therefore their users) about what (parts of) programs are able to access like they do now.

  4. privacyishuman

    https://xitter.cf/GrapheneOS/status/2122079826257588569#m

  5. __MatrixMan__

    I don't think this is an accurate description of why linux was created. But I do think it's time to design something that better fits the needs of the modern world.

    We need another Bell Labs.

More from this day

2026-11-16