Well, it did take us a few thousand years to get to safe wooden buildings... I actually don't think securing C/C++ code is that hard. It's certainly a skill yo

Well, it did take us a few thousand years to get to safe wooden buildings... I actually don't think securing C/C++ code is that hard. It's certainly a skill you need to learn, but so is writing linked lists and qsort. I think people just aren't applying themselves. But the language seems to catch the flack rather than the programmer. From the article: The bug is that there is simply no bounds checking at all; sig and key are arbitrary-length, attacker-controlled blobs, and cx->u is a fixed-size buffer. As we can see, the programmer just made no effort to secure the code. But we still blame the language, like blaming wood for being flammable. Anyway. I'm definitely not against new languages. But I think before a program is rewritten, it should be for a reason much better than "I didn't want to secure the code".