a b c d e f g h i j k l m n o p q r s t u v w x y z

diff from 76861 and 2491

Description: examines source code and looks for security weaknesses
 Flawfinder searches through C/C++ source code looking for potential
 security flaws and produces a report describing the potential flaws
 found in source code, ranking them by likely severity.
 .
 Like RATS, Flawfinder reports are not a direct indication of a
 vulnerability, but provide a reasonable starting point for performing manual
 security audits in source code.
 .
 Flawfinder can also generate differential reports by pointing it to
 a patch (diff) file describing the code changes. This way it can be used
 to determine if the potential flaws found in code have increased or
 decreased after a commit to a source code management system like
 CVS or Subversion.
Description: examines source code and looks for security weaknesses
 Flawfinder searches through C/C++ source code looking for potential
 security flaws, ranking them by likely severity.
 .
 Flawfinder intentionally works similarly to another program, ITS4,
 which is not open source.
 .
 The flawfinder homepage is http://www.dwheeler.com/flawfinder/
--- 76861	Thu Jan  1 00:00:00 1970
+++ 2491	Thu Jan  1 00:00:00 1970
@@ -1,14 +1,8 @@
 examines source code and looks for security weaknesses
  Flawfinder searches through C/C++ source code looking for potential
- security flaws and produces a report describing the potential flaws
- found in source code, ranking them by likely severity.
+ security flaws, ranking them by likely severity.
  .
- Like RATS, Flawfinder reports are not a direct indication of a
- vulnerability, but provide a reasonable starting point for performing manual
- security audits in source code.
+ Flawfinder intentionally works similarly to another program, ITS4,
+ which is not open source.
  .
- Flawfinder can also generate differential reports by pointing it to
+ The flawfinder homepage is http://www.dwheeler.com/flawfinder/
- a patch (diff) file describing the code changes. This way it can be used
- to determine if the potential flaws found in code have increased or
- decreased after a commit to a source code management system like
- CVS or Subversion.