Re: Suggestions for nmap

["DePriest, Jason R." <jrdepriest () gmail com>]

Hello, Kert.

The features you want are already implemented.

If you run nmap with a 'verbose' option like -v it should show you
what it finds as it finds it and if you hit <enter> while it is
running, it will give you its best estimate for how long the current
stage will take to finish.

man nmap or http://insecure.org/nmap/docs.html

-Jason

On Jan 10, 2008 3:51 PM, Jans, Kert wrote:
> Hi,
>
>   I just used nmap to perform a port scan...
>   unfortunately it (or something else) failed after 20 hours and I lost
>   the results of the scan...
>
>   I have two suggestions for improvements to nmap.
>
>    1) provide a command-line option to print out just the open ports
>       "as they are found".  With this, I would have been able to see the
>       ports it found before the crash.  I tried the verbose and packet
>       tracing options... but that is too much information.
>
>    2) the feature of nmap that allows the "percent complete" status to
>       be reported when any character from stdin is entered, is nice.
>       It would be real-nice if there was a special command-character
>       (like v/d/p) that caused the current results to be printed.
>       This way I could have looked at snapshots of the progress during
>       the 20 hours of the scan.
>
> Regards,
> Kert
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org



-- 
NOTICE:  Reading this email message requires root privileges which you
do not appear to possess. Sorry, dude.

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org