Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Nmap Development: Re: Flushing output

Re: Flushing output

From: Nils Magnus <magnus_at_linuxtag.org>
Date: Sun, 8 May 2005 04:00:41 +0200

Re,

On Sat, May 07, 2005 at 03:06:32PM +0000, grutz wrote:
> Here's something I'd like to see added that would help with rate-limited
> testing: really flushing out all the information nmap currently has
> about a host when interrupted with a SIGINT. It sucks to have been
> scanning 65535 ports on a subnet of 4 machines, have 3 of them be
> completed while one just sort of sits there, slowly responding. If you
> send nmap a SIGINT (^C) while it's hung on the last machine you don't
> get any information in the output other than the scan info. Now you have
> to rescan the previous hosts again.

That's why I suggested some time ago to introduce a handler for SIGUSR1
or something that makes nmap flush all data on a current host (or set of
target hosts) and move on to the next one.

Regards,

Nils Magnus
Program-Chair LinuxTag 2005 Free Conference Program

LinuxTag 2005: Where .com meets .org - magnus_at_linuxtag.org

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Received on May 07 2005

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos