4 ms·
This thread here: http://openssl.6102.n7.nabble.com/Coverity-coverage-of-OpenSSL-td42651.html http://openssl.6102.n7.nabble.com/Coverity-coverage-of-OpenS...
by ThursdayNext 13y ago
This thread here:
http://openssl.6102.n7.nabble.com/Coverity-coverage-of-OpenSSL-td42651.html http://openssl.6102.n7.nabble.com/Coverity-coverage-of-OpenS...
mentions that one OpenSSL developer used to see defect reports from Coverity (probably through Coverity's scan project). He states:
"Coverity used to, and perhaps still do, run scans of OpenSSL, which we had (have?) access to. I used to look at them and fix relevant ones, but got irritated with the false positive level in the end.
If Coverity were interested in fixing their bugs, I might get interested in looking at their reports again."
Of course this doesn't demonstrate that Coverity found this particular problem, and since he doesn't state what the false positive rate was it's difficult to know how reasonable his statement is.
- shagie 13y agoAccording to Andy Chou of Coverity on Twitter https://twitter.com/_achou/status/454287263917043712 https://twitter.com/_achou/status/454287263917043712 - "We looked at the code and it turns out the bug is caused by something we don't currently detect." and then goes on to say "But we're going to look into it further. In cases like this it is not only about finding the defect it's also about not flagging hundreds/thousands of false positives at the same time" So no, Coverity wouldn't find it.