To read all comments associated with this story, please click here.
I'm kidding. Mostly.
Heh. In all fairness though, BIND security has improved substantially over the last few years. Don't know about sendmail since I've abandoned it completely in favor of postfix and lately qmail again, now that it's got a workable license.
Yeah, I also have to rise in the defense of BIND. One of my past jobs involved static code analysis for a large software project, and we were evaluating whether or not to license Coverity Prevent. In order to judge its merit, I was to select an open source project and compare the Coverity results to the those from another analysis tool that we'd been using for some time.
I initially picked BIND, since it's well-known and the defect rate from Coverity was very low. I figured it would be a good showcase for comparing the performance of the tools on high quality code. The problem was, when I ran the other tool on BIND, it hardly found any real defects at all. I was shocked. In order to produce more meaningful results, I settled on the FreeBSD kernel. That produced plenty of data.
During my time investigating BIND, I really liked what I saw. Most functions begin with a set of assertions. It has its own uber-paranoid memory allocator that's used universally across the codebase. BIND is a very solid piece of code. Respect.
Coverity Prevent is also an outstanding static analysis tool. Definitely the best out there by far. It's pretty damn expensive for proprietary projects (it can run several million dollars for a large codebase), but it's free (beer) for any free software project as long as Coverity is credited in the bug reports. Every free software project ought to be running Coverity as a part of their development and release processes. Most of the bigger projects like Linux and Apache have already been running it for years.






Member since:
2005-07-06
That figure does include some PHP. Did they include bind and sendmail as well? That would just be unfair.
I'm kidding. Mostly.