Re:The alarming state of secure coding neglect
by lawnchair_larry on Wednesday May 03, 2017 @10:24PM
(#14261951)
Yep, this is the only thing that can possibly work. The path of least resistance has to be secure, and in order to do something insecure, you need to know enough about what you're doing to jump through hoops to get there. Right now, we are in the opposite situation. People have to jump through hoops to do the secure thing.
You also have to meet them where they are, not get them to change their ways to suit yours. Otherwise, you're adding resistance, and you'll fail.
A good start would be to stop using C and C++ for new projects, and generally try to eradicate undefined behavior at all levels of software. There's a lot of really great software written in C and C++, and it would be a huge undertaking to replace, say, the Linux kernel with something written in Rust or Swift or some language that hasn't been invented yet. I think the eventual benefits may greatly outweigh the costs, but it's a lot easier to sit in a local optimum where everything is comfortable and familiar than to set out on a quest to, say, formally verify that no use-after-free errors or race conditions are possible in any of the software running on a general-purpose computer with ordinary applications.