Dan, On Fri, Nov 21, 2008 at 10:08 AM, Andres Riancho <[EMAIL PROTECTED]> wrote: > Dan, > > On Fri, Nov 21, 2008 at 1:48 AM, Dan Guido <[EMAIL PROTECTED]> wrote: >> I was hoping for something that just said which plugin you were >> currently in, rather than a progress bar. So if I'm sitting at the >> console for 20 minutes and I press the space bar then I know it's XYZ >> plugin that is taking forever so I can run the scan again without it. > > Ok, I'll add this to the feature request list.
I just commited the console user interface change that adds the status feature. Please test it, and let me know if that was what you needed. To actually "get to the feature", after executing start, you get the status by pressing enter. I also modified the documentation to let the other users know of this feature. In the future, I'm planning to show a progress bar and a ETA, but that's for the weekend ;) >> Also, I'm getting crashes on xUrllib during discovery, probably >> related to the crawler. In this particular instance I was trying to >> crawl a forum and it probably tried getting each forum thread (ever) >> :-(. > > The time issue is because it's crawling all the threads. > The crash... report them to me and I'll fix them > > Cheers, > >> -- >> Dan Guido >> >> >> >> On Thu, Nov 20, 2008 at 10:10 PM, Andres Riancho >> <[EMAIL PROTECTED]> wrote: >>> Dan, >>> >>> On Thu, Nov 20, 2008 at 9:44 PM, Dan Guido <[EMAIL PROTECTED]> wrote: >>>> Hey Andres, >>>> >>>> When w3af_console is scanning, can you catch keypresses and show us >>>> where in the scanning process we are? >>> >>> I could... but only in the audit phase. In the discovery phase, w3af >>> never knows if the next plugin is going to find 100 more links or zero >>> links, so saying "we are 80% complete" in the discovery phase would be >>> a lie. Maybe it could be a progress bar that says "80%" , "60%", >>> "70%"... "100%". But I'm not very happy with that behavior. What do >>> you think? >>> >>> I could easily code this, but please help me define specifically what >>> you want, and what others users may find useful and I'll do it in such >>> a way that the core provides the information, and the console user >>> interface and the graphical user interface can show it in their own >>> way. If I do it, i'll do it the right way ;) Before having the gtkUi, >>> the console had a progress bar, which was removed because it simple >>> broke the log screen in the gtkUi, so I could re-use that code for the >>> consoleUi and use generic progress bar for the gtkUi. >>> >>> Cheers, >>> >>>> -- >>>> Dan Guido >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>>> challenge >>>> Build the coolest Linux based applications with Moblin SDK & win great >>>> prizes >>>> Grand prize is a trip for two to an Open Source event anywhere in the world >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>>> _______________________________________________ >>>> W3af-users mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/w3af-users >>>> >>> >>> >>> >>> -- >>> Andres Riancho >>> http://w3af.sourceforge.net/ >>> Web Application Attack and Audit Framework >>> >> > > > > -- > Andres Riancho > http://w3af.sourceforge.net/ > Web Application Attack and Audit Framework > -- Andres Riancho http://w3af.sourceforge.net/ Web Application Attack and Audit Framework ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ W3af-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/w3af-users
