News for hackers. Stuff that matters.
Re:Glibc getaddrinfo stack-based buffer overflow by viraptor on Tuesday February 16, 2016 @11:19PM (#11115270)
Are you arguing that since we can't replace everything with safe code, we shouldn't replace most of it? Security is not a binary state. Even taking firmware into account, if you compare the number of CVEs affecting "normal code" and firmware, the choice is trivial.
Re:Glibc getaddrinfo stack-based buffer overflow by ptaipale on Wednesday February 17, 2016 @10:35AM (#11118489)
> Are you arguing that since we can't replace everything with safe code, we shouldn't replace most of it?

Well, yes, the effort to replace even a small part of current code base with something perceived as "safe code" is huge. The re-factoring effort is so great that there is no doubt a significant number of new seurity problems wouldn't be created.

They would of course be different kind of problems. Not indexing errors, perhaps, but something we don't even know about. And justifiying this very large cost is not so easy.