3 ms·
How many bugs in qmail though?
by inigyou 4mo ago
How many bugs in qmail though?
- himata4113 4mo agoIt had one bad cve it seems, but that's exactly what I mean. It only takes one mistake, of course you can learn and never make those mistakes again, however, that is an unrealistic expectation in software that receives hundreds of feature updates a year especially when it comes to core applications as basic as communication when it wants to support image previews, reels and whatnot.
- Brian_K_White 4mo agoThere will always be one, so "it only takes one" is meaningless and invalid. That leaves less is better than more, and any form of less is as good as any other form of less.
- deleted 4mo ago[deleted]
- inigyou 4mo agoSome Rust programs also had RCE CVEs.
- Ygg2 4mo agoSome is doing heavy misrepresentation. Latest batch of LLM's Linux had 423 vulnerabilities. Out of which 10 were Rust*. Would you prefer more or less CVEs? But it's like seat belt analogy. It's a helper not a panacea. * Granted Rust isn't in the entire kernel yet. D
- inigyou 4mo agoThat sounds like Linux has more vulnerabilities per line of Rust code than line of C code, given the language ratio...
- Ygg2 4mo agoSure, but C code is way older so most of the bugs there should have been excised by now...
- ssokolow 4mo agoHere's a better exploration of defect rates: https://security.googleblog.com/2022/12/memory-safe-languages-in-android-13.html https://security.googleblog.com/2022/12/memory-safe-language...
- himata4113 4mo agoThis is pretty hard to argue since for example: WireGuard is a finished piece of software. It gets: no feature updates, was designed in-full before a single line of code was written and has stood the test of time. You cannot compare that to some desktop application that has a thousand features with 100's more added every year.
- fmajid 4mo agoAnd its transition to post-quantum cryptography is going to be a migration challenge.
- kelnos 4mo agoI don't think we should set our expectations based on an extreme outlier. qmail is special, and we can't expect most software to get to its level of security/safety. Put another way: if you have to rely on programmer skill or attention to detail in order to guarantee something, that will always be a losing bet, on average. The existence of a tiny percentage of programmers that can clear that high bar does not make it a valid strategy.
- inigyou 4mo agoWhy can't we write everything like qmail?
- uecker 4mo agoSplitting programs into mutually untrusting modules is a plausible alternative to memory safety in programming languages. Also in a program similar to qmail, memory safety alone is not sufficient, a lot of bugs in sendmail were related to complexity issues.
- pjmlp 4mo agoIf only there was an OS design architecture that would follow such approach from the ground up....