On Wed, Apr 11, 2012 at 4:56 AM, Taras <ox...@oxdef.info> wrote: > Andres, > > >>>> If the framework IS working like this, I think that the shared >>>> fuzzable request list wouldn't do much good. If it is not working like >>>> this (and I would love to get an output log to show it), it seems that >>>> we have a lot of work ahead of us. >>> >>> >>> And w3afCore need to filter requests from discovery plugins on every loop >>> in >>> _discover_and_bruteforce(), am I right? >> >> >> It should filter things as they come out of the plugin and before >> adding them to the fuzzable request list, > > Agree, but as I see in w3afCore.py there is no filtering in it. > I just have added it [0]. It shows good results on the test suite (see > attachment). > > Without filtering: > Found 2 URLs and 87 different points of injection. > ... > Scan finished in 3 minutes 30 seconds. > > With filtering: > Found 2 URLs and 3 different points of injection. > ... > Scan finished in 11 seconds.
Reviewing this and reproducing in my environment. Will have some opinions in ~1h > > >> Please let me know if the discovery process is NOT working as we >> expect and if we have to filter stuff somewhere > > See above. > > [0] https://sourceforge.net/apps/trac/w3af/changeset/4861 > -- > Taras > http://oxdef.info -- Andrés Riancho Project Leader at w3af - http://w3af.org/ Web Application Attack and Audit Framework ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
