Post #1887764
2026-04-29 09:56 UTC
Replies (5)
-
@Archivist@social.linux.pizza 2026-05-04 14:26
@swick@hachyderm.io except there were cves related to memory safety in uutils as well
-
@alg0w@social.vivaldi.net 2026-04-29 10:14
@swick The key word is "security-minded". Everybody wants their code to become automagically safer. My maybe controversial opinion is the most Rust folks aren't security minded at all. Memory safety isn't the only thing, JS is memory safe and is used even in embedded programming ;) Also IMO most C problems come from bad and old standard library, which was designed when security wasn't a real issue. You shouldn't just use most functions in it. And as a last note if folks would've been really serious about security they would've chosen #Ada programming language.
-
@Qbitzerre@unbound.social 2026-04-29 10:24
@swick the allure of a panacea.
-
@federicomena@mstdn.mx 2026-04-30 01:12
@swick Most of these bugs smell similar to "my first file manager" kind of code. I guess everyone has to learn by screwing up :)
-
@zeenix@toot.cat 2026-05-01 13:51
@swick I only know one **very** specific fs API "issue" that Lennart keeps talking about and that one: 1. Is not an issue for a vast majority of software and hence why nobody thinks about it. 2. Can be easily prevented by using a crate specifically designed for it. 3. IIRC hard to abstract in a cross-platform manner. Are there other issues like that that exist "because of std"?