-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 6/18/07 1:42 PM, Tim Brown wrote: > Ok, so after hacking around with the web site a little and > attempting a build on a clean VM image, my thoughts are turning to > the plugins which are in urgent need of update to check for new > vulnerabilties. Some thoughts from an initial perusal of the tree: > > > Merging the local checks for each platform? This can be done, and > in fact I think these checks could be built in an automated > fashion, at least on Debian. What do people think? > > Web application checks appear to be tested rather arbitrarily, with > some checks within application scripts, some in dangerous_cgi.nasl > etc... It all seems a bit haphazard. Now applications is an > interest of mine, and indeed I have a number of checks to add, but > what are peoples thoughts about how to organise these checks? How > about with directory traversals and file include flaws? > > Finally, to what level do people feel it is necessary to check > flaws such as stack and heap overflows? Where possible just > validate by version? Or some more in depth form of check? What > happens if we can't get a version number back from the application? > > > My ideal world would be 1 OSVDB entry, 1 script and validate to > whatever level allows confirmation that the bug really exists, but > let me know what you think. > > My ideal world would have a single plugins.xml file that contains all the checks. At the very least one file per (year, platform, etc). I was not successful in arguing for this change earlier however. I think the idea of single file checks is antiquated and the only reason we have held on to it is because Nessus does. I can't think of another vulnscanner which still keeps their plugins in individual file format. Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGdwRk5Kv+lIJNcCARAhXTAJ4psjSZ6ypCkdaheaQ26QBCkUu2OgCgoXih Cv6E8/D3mMEcsfmo+tiVRLk= =T5B0 -----END PGP SIGNATURE-----
_______________________________________________ Openvas-plugins mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-plugins
