New Kernel Vulnerability Allows Local Root For Unprivileged Processes

[starshipeleven]

No. It is a pun on the sentence "If you care about security you should be using Linux." which is like saying: "If you care about security, you should be using an OS with obvious security holes."

But... but... the OS with obvious security holes is Windows, not Linux.

If this security hole was obvious it would have been detected and patched long ago, not like 5 years later.

[vadix]

of course all real code which is "written in garbage collected language" is actually written in a mix of garbage collected and native languages. and memory safety is not the only kind of safety required. just look at crashes of java apps. btw, really real code has not enough of either memory or cpu cycles for garbage collector

Just so you know, the entire Rust package manager, Cargo, is written in entirely safe code. You wrap unsafe code into safe APIs in Rust. While the process isn't infallible, it is definitely possible to write incredibly large applications without any unsafe code. As for a kernel, you will likely need unsafe regularly when dealing with hardware and memory, but overall the amount of unsafe blocks can be limited to small regions of code so that an audit is more efficient.

[pal666]

You wrap unsafe code into safe APIs in Rust. While the process isn't infallible, it is definitely possible to write incredibly large applications without any unsafe code.

i see mutually exclusive paragraphs here. and there is no incredibly large applications written in rust. btw, safe/unsafe is false dychotomy, see for more powerful solution https://www.youtube.com/watch?v=hEx5DNLWGgA