News for hackers. Stuff that matters.
Re:How undefined signed overflow enables optimizations in GCC by pekk on Monday February 22, 2016 @12:41AM (#11148761)
I'm sorry if you feel gcc maintainers are unappreciated, that's not good. Clearly no compiler can rescue programmers from every security mistake they might make.

But raising security concerns is not "entitled," insecure-by-default is not okay, and "it's fast and the standard lets us get away with it" is not a sufficient defense.

Maybe non-conforming code should be penalized by making it slow, not by causing another large-scale public scourge like Heartbleed. Such risks are not just between gcc maintainers and inept programmers, there's a lot more at stake than that.

Re:How undefined signed overflow enables optimizations in GCC by PeCaN on Monday February 22, 2016 @01:57AM (#11149051)
Doing something that you _know_ is wrong, then complaining when the compiler happens to break it, is entitled if I've ever seen it.

I don't think I would trust code that relies on undefined behavior to be secure. That doesn't really sound that safe.