News for hackers. Stuff that matters.
Re:A critique of "How to C in 2016" by benbenolson on Friday January 15, 2016 @08:48AM (#10909240)
Those are due to programmer error. The fact that C doesn't lie to you means that it takes a bit more experience to program properly; as with all things, with great power comes great responsibility. You don't blame the gun for killing people, you blame the person for shooting it.
Re:A critique of "How to C in 2016" by whyever on Friday January 15, 2016 @09:16AM (#10909396)
> Those are due to programmer error.

How does that help? Almost all security vulnerabilities are due to programmer error.

> You don't blame the gun for killing people, you blame the person for shooting it.

It's more like choosing between a gun that makes it really easy to shoot yourself in the foot by accident and one that is safer.

Re:A critique of "How to C in 2016" by legulere on Friday January 15, 2016 @09:11AM (#10909356)
Not even the very best C programmers will write memory safe code. When you write C you will write exploitable code, no matter who you are. Don't blame the programmer for stepping onto a mine in the minefield, blame the minefield.