Memory Corruption Vulnerability in Linux "Memory Safe" Rust Code

Coffee break
1
2 Likes
2

For some reason, I keep thinking ”Embrace, Extend, and Exterminate.”

FOSS is basically under attack by Daleks.

2 Likes
3

A count of the number of usages of unsafein *.rs (rust) files from the latest stable kernel 6.18.1 source tarball:

$ basename $PWD ; grep -r --include \*.rs -E "unsafe {.*?\}" . | wc -l
linux-6.18.1
1495
5 Likes
4

Yikes

3 Likes
6

O ja pierdole Ho Lee Fuk

2 Likes
7

To be fair
”Rust uses unsafe because:

  • low-level programming requires it

  • compilers can’t prove everything

  • systems programming needs escape hatches

But Rust makes unsafe:

  • explicit

  • localized

  • auditable

  • optional for most code”

Ok I understand that. It is literally imposible to produce 100% safe and bullet proof code in any language. I would never argue with above list in case of anyother language but rust. Why you may ask?
Because main selling piont of rust and one and only talking point of it’s zelots is safety memory safety. Rust is safe rust is always safe if you thing otherwise you a bad and stupid person who is…(put any insult you see fit here ).

Im tired of those idiots, not the rust it self. How can I trust a language if it is mainly used by unstable people. Let just put aside the problematic licence of this language and few other things

1 Like
8

I think if it was not for the propaganda, cult mentality and absolute moron behavior of Rust promoters, people would more easily accept and use it. [/obvious]

9

everytime you get forced to do some stuff you don’t like you develop some feelings against that said thing

3 Likes