Re: Your opinion on a valuable and feasible goal for a new source code auditing tool

I've never seen this done right (essentially, because it's not an easy
thing to do).  But if you can track all input data AND know where it can
cause problems (at various system calls, etc), then you would have
created the ultimate source-code auditing tool, since false negatives
would be reduced dramatically without losing precision.  

Probably impossible to do without some sort of sandboxing, though.  

-- Jordan Dimov
VP, Association for Information Security
http://www.iseca.org/


On Tue, 2004-05-11 at 17:56, Jose Nazario wrote:
> have a look at CQUAL, it does sort of what you want to do (taint
> checking). while it does a good job, it's not terribly easy to do. you
> could marry flow control analysis to input tagging and tracking and
> essentially make it easier for the developer to use.
> 
> ________
> jose nazario, ph.d.                   [email protected]
> http://monkey.org/~jose/              http://infosecdaily.net/
>