News for hackers. Stuff that matters.
Re:Apple's SSL/TLS bug by pjmlp on Saturday February 22, 2014 @10:01AM (#7282208)
There is no excuse to bypass static analysis nowadays. At very least should be part of the continuous integration build.

The problem are the many developers that still think they are perfect and know the full C standard, including undefined parts.

Re:Apple's SSL/TLS bug by eliteraspberrie on Saturday February 22, 2014 @02:22PM (#7283205)
Unfortunately the decision to use static analysis tools would have to come from developers who are comfortable admitting they make mistakes sometimes.

It takes a special kind of ego to write an SSL library with no unit tests, not turn on compiler warnings, and not use static analysis tools.

Re:Apple's SSL/TLS bug by TwoBit on Saturday February 22, 2014 @03:11PM (#7283401)
Re:Apple's SSL/TLS bug by MrBuddyCasino on Sunday February 23, 2014 @06:25AM (#7285597)
Wow. Thats really bad, who would have thought OpenSSL is such a piece of crap? Its about time someone writes a decent alternative!
Re:Apple's SSL/TLS bug by pjmlp on Saturday February 22, 2014 @03:34PM (#7283476)
Very enlightening.
Re:Apple's SSL/TLS bug by pjmlp on Saturday February 22, 2014 @03:02PM (#7283360)
Fully agree, I met quite a few of those egos already.
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