News for hackers. Stuff that matters.
Re:Apple's SSL/TLS bug by laureny on Saturday February 22, 2014 @10:44AM (#7282371)
That's a rare problem among developers. The more common problem is that developers make mistakes. All of them.

Static analysis, regression tests and turning on all the warnings you possibly can should be mandatory, especially for such critical pieces of code.

Re:Apple's SSL/TLS bug by erichurkman on Saturday February 22, 2014 @12:01PM (#7282638)
And if you are going to disable a specific warning, it should only be for a limited section of code and include a detailed comment about why the warning is superfluous and why the code is safe.
Re:Apple's SSL/TLS bug by pjmlp on Saturday February 22, 2014 @11:26AM (#7282515)
> That's a rare problem among developers.

Many of the C guys I met along my career thought otherwise.

> Static analysis, regression tests and turning on all the warnings you possibly can should be mandatory, especially for such critical pieces of code.

+1