Nmap Development mailing list archives
Safely killing nmap
From: Richard van den Berg <richard.vandenberg () ins com>
Date: Fri, 13 Jan 2006 08:48:21 +0000
I was running nmap 3.95 with nmap -sS -sU -sV -p- -O -p- -oA -vv -T4 outfile 1.2.3.4/27 where 1.2.3.4 is our local subnet. It went through the TCP stuff quite fast, but the UDP took a long time. So far so good, but the version scanning on the UDP ports again was about to take forever. So I decided to kill it. I was surprised to see that after completing the full TCP and UDP scans, no results were writen to the output files. It seems that sigdie() which handles the killing of the process flushes and closes the output, but does not actually write any results still left in memory. I can understand that no intermediate results were written (because the grepable and xml format need to know all information before making the report), but it would have been nice to not have the scan be wasted just because I decided to stop it early. Is there any way I could have made nmap save the report before/while killing it? Sincerely, Richard van den Berg _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev
Current thread:
- Safely killing nmap Richard van den Berg (Jan 13)