Maxime Villard has been doing great work finding lots of bugs, many with a code scanner he wrote called Brainy. As an OpenBSD user I've been watching with interest from the sidelines. More info on Brainy results:<p><a href="https://www.m00nbsd.net/474b193ce624a19d39a2286d73f06826.html" rel="nofollow">https://www.m00nbsd.net/474b193ce624a19d39a2286d73f06826.htm...</a><p>Take a look! There is likely software that you use in the list - for instance, one of the bugs is a memleak in OpenSSH.<p>I don't use NetBSD but I just donated $20 to the NetBSD Foundation anyway. Thanks for sharing code/patches!
How does one go about conducting such audits? Is it just a case of looking at the code long with an experienced eye to spot potential flaws? Or are there standard techniques and tools that people follow?
>I stumbled across a PR from 2010, which was briefly saying that PF’s TCP-SYN entry point could crash the kernel if a special packet was received. Looking at the PF code, it was clear, after two minutes, where the problem was.<p>I wonder how often problems like this languish in bug trackers (due to a shortage of developer availability? flood of low-quality bugs? other problems?)
This is great news. Since they took a beating in the last security findings in code that was not even enabled by default. Leading to it seeming much more serious than it was.