News for hackers. Stuff that matters.
Re:Don't run 'strings' on untrusted files by CamperBob2 on Saturday October 25, 2014 @03:55PM (#8509210)
How would that fix the problem at hand? The code in question isn't using array notation. At the end of the day, it's not a case of using C when another language would be better, it's a case of crappy coding.
Re:Don't run 'strings' on untrusted files by WalterBright on Saturday October 25, 2014 @04:03PM (#8509234)
It helps because instead of rewriting the whole app, just the function parameter types are redone where pointers to data are changed to bounds checked arrays, on a case by case basis.

It isn't a magic bullet, but as buffer overflows are (I presume) the most common cause of C security exploits, this would help a lot.

Re:Don't run 'strings' on untrusted files by CamperBob2 on Saturday October 25, 2014 @04:41PM (#8509322)
Maybe, but my fear would be that the act of rewriting it to use array notation will introduce yet more bugs. Some of the comments point out that the problem exists because nobody cared enough to fix it for several years. Having seen that nobody cared enough to fix it, it's not clear that anyone will care enough to fix it properly.