Hello, I said quick in the sense of usability, not runtime. Currently, to run a scan, a user must open Umit, wait until it loads, type in the target, move the mouse or directional keys to select a profile and hit enter. After that, he receives a parsed data which is not much interactive yet. In the context of terminal, people must type in a nmap command, remind all the options he needs and get an even less interactive result. The goal is to be quick, in the sense of removing as much steps as possible from a user to think of making a scan and having the result on the screen.
Cheers! Em 27 Mar 2009, às 10:49, neeraj gupta escreveu: > Hello, > > I saw Adriano's thread and was wondering how can one make quick scan > more faster than it is, when umit itself uses Nmap to parse the > data. So the quick scan cannot be quicker than nmap unless we code > the scan by ourselves. Is that what is required? Please clarify. > > Regards > Neeraj > ------------------------------------------------------------------------------ > _______________________________________________ > Umit-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/umit-devel --- Adriano Monteiro Marques http://www.thoughtspad.com http://www.umitproject.org http://blog.umitproject.org http://www.pythonbenelux.org "Don't stay in bed, unless you can make money in bed." - George Burns ------------------------------------------------------------------------------ _______________________________________________ Umit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/umit-devel
