I love Rust, but not THAT much.

https://blog.qualys.com/vulnerabilities-threat-research/2021/01/26/cve-2021-3156-heap-based-buffer-overflow-in-sudo-baron-samedit
https://github.com/uutils/coreutils/issues/8573
https://github.com/uutils/coreutils/issues/8583

Next time you hear zero-trust solutions, try ThreatLocker, and tell them Low Level sent you @ https://go.lowlevel.tv/threatlocker 

🏫 MY COURSES
Sign-up for my FREE 3-Day C Course: https://lowlevel.academy

🧙‍♂️ HACK YOUR CAREER
Wanna learn to hack? Join my new CTF platform: https://stacksmash.io

🔥COME HANG OUT   
Check out my other stuff: https://lowlevel.tv

Low Level Learning

The GNU community is rewriting Linux core utilities in Rust for memory safety, but early implementations show significant problems. The Rust version of 'sort' fails on large single-line files, and the checksum implementation runs 17 times slower than the C version. While Rust rewrites make sense for security-critical binaries like sudo that cross privilege boundaries, most core utilities don't have meaningful threat models that justify the performance and compatibility risks of rewriting battle-tested C code.

rust is causing a lot of problems...

If it ain’t broken, don’t fix it

Sadly enough; these rewrites are not driven by security concern. There’s a huge hype about Rust that companies like Canonical want to exploit into free development time or cheap hires. Moreover there’s a licensing benefit. The more GPL binaries get replaced, the easier they can make proprietary software based on their MIT versions.
I can imagine Ubuntu Pro 28.04 may have something not available to the community version just because of this licensing difference (and I’m not talking about extended security updates and live kernel patching that they already do).

Ok, so fix the ‘sort’ then dear Rust owners - thx!

well you exaggerate the problem that single line file storage is 4.1GB size well it happens in rare scenario not day to day so try to be practical.