No, that's not what I've been saying. I think it would be a serious regression to break compatibility with safe implementations by making it correct to be incompatible with them. You want to massively roll back safety and security, especially if you want to remove it by default.
Conversation
It's not a big deal if the spec says that overflow wraps. Anyway, a most useful version of trap-on-overflow would do this for unsigned, which isn't allowed in the current spec. It's fine to have security technologies that create interesting new behaviors.
2
The "breaking interface contracts is a security enhancement" view is a very very harmful one. It's the opposite.
3
7
Systems code should be written in something higher level than assembler but lower level than the symbolic execution system that C claims to provide currently. “Just use assembly” or “just use a type safe language” aren’t useful answers.
1
Systems code benefits from memory and type safety even more than most other code because it's often in a position of trust and privilege. Using a language where unsafety can be contained and quickly wrapped into safe APIs is certainly useful advice for newly written systems code.
1
2
6
The expectations of software robustness and security have increased a lot, and it's simply not realistic to achieve it while using unsafe tools making it much more difficult to write safe code. Writing something complex like an safe ext4 implementation is C is not very realistic.
1
5
i.e. writing the entire thing with zero memory corruption bugs for an attacker to exploit either via an attacker controlled filesystem or an application. Drivers similarly have to be written treating the hardware and code using them as adversarial. Choice of tools is important.
1
2
This Tweet was deleted by the Tweet author. Learn more
This Tweet was deleted by the Tweet author. Learn more
That's a completely ridiculous claim. Even when looking at an OS as a whole, rather than just the systems level portions, memory corruption bugs are the majority of the vulnerabilities.
zdnet.com/article/micros
Bugs caused by unsound / weak typing are a decent portion too.
1
Integer overflows are most often exploitable when they lead to issues like heap corruption, but are still a common source of issues beyond that. There are other common classes of bugs, and for many of them, we know how to easily prevent or catch these issues for most of the code.
There are certainly other kinds of bugs. Systemic approaches like reducing the trusted computing base are important. Having a massive, completely trusted monolithic kernel isn't a workable approach to making a decently secure OS but having memory safety for 95% of it would help.