It’s worse! Because in addition to SQLI, file access vulns, and races, you also get memory corruption.
One outcome of my taking on kernel work might be gaining enough experience to redo it right. :-)
-
-
It really needs a many-pronged approach, and the Linux kernel is failing at every aspect of improving security.
-
Moving more code into the kernel, instead of moving towards a microkernel like competing operating systems.
-
And sticking with using entirely C, instead of migrating towards a safe language for new / rewritten components.
-
I don't see any viable alternatives to C for robust kernel programming, but Linux doesn't even use C robustly.
-
Idiotic things like malloc'ing & refcnting struct cred rather than putting it in task struct directly.
-
There are viable alternatives to C, like Rust without any of the standard libraries above the layer of libcore.
-
Maybe someday, but for now I don't see how a language whose spec isn't even near-stable is usable for kernel..
-
It's not like the C specification is stable... and it only gained a memory model with C11, which is a big deal.
- 10 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.