Re:CWE Top Most Dangerous Software Weaknesses
by UncleMeat on Thursday July 13, 2023 @10:16PM
(#36718665)
Having spent well over a decade in this space, I assure you that the root cause of limitations for static analyzers doing lifetime analysis in C++ is not separate compilation or partial program analysis caused by shared libraries.
Naturally it isn't.
Again, even if not perfect, and doesn't cover all use cases, what about people would actually use something at all?
During that decade, how much time did you spent looking at the human side of the problem instead of what the tools can achive?
Re:CWE Top Most Dangerous Software Weaknesses
by UncleMeat on Friday July 14, 2023 @08:48AM
(#36723186)
Nowhere did I suggest that we shouldn’t use these tools or spend time improving them. UX for tools more powerful than local AST matching indeed tends to be quite bad because explaining the chain of reasoning for an alarm is difficult.
My only point is that without a different approach we will continue to have the same problems in 2073.
The main issue is the community sub-culture of not adopting tooling as it isn't perfect 100% of the time.
Many of the C++ security conscious folks end up being polyglot, as this subculture eventually wears one out.