|
Nmap Development
mailing list archives
Re: Ctrl-C annoyance
From: alex medvedev <alexm () pycckue org>
Date: Tue, 6 Apr 2004 18:36:27 -0500 (CDT)
hallo again,
here is a small fix to the patch i posted last week in case somebody would
want to really use it.
it checks if the list of ports is not empty before outputting:
+ if (currenths) /* it may be empty */
+ printportoutput(currenths, ¤ths->ports);
+ else /* daaang... a fast ctrl-c'er... */
+ fprintf(stderr, "nothing yet... be patient...\n");
so, if there exists a really fast ctrl-c'er, she wouldn't be able to make
nmap segfault in the very beginning of its execution when no data had been
collected yet.
the files attached are a cumulative patch.
-alexm
18:24 06/04/2004
PS: pls CC me if you want to contact me as i am not on the list.
On Mon, 29 Mar 2004, alex medvedev wrote:
hi,
i do not use nmap frequently, nor do i scan very often...
but when i do i am always surprised why nmap does not report anything when
Ctrl-C is pressed and simply runs a cleanup.
when scanning slow networks or firewalls that filter everything nmap may
just sit there for many minutes.
here is a small patch that prints out the ports "collected so far" when
the Ctrl-C combination is pressed.
when Ctrl-C is pressed 3 times it simply quits nmap.
i didn't bother to check what i broke, but i made currenths global
in main.cc
-alexm
17:50 29/03/2004
Attachment:
main.cc.diff
Description:
Attachment:
nmap.cc.diff
Description:
---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to
nmap-dev-help () insecure org . List archive: http://seclists.org
By Date
By Thread
Current thread:
- Re: Ctrl-C annoyance alex medvedev (Apr 06)
|