Home page logo

nmap-dev logo Nmap Development mailing list archives

Re: 4.49RC7 NSE Loop?
From: Stoiko Ivanov <stoiko () xover htu tuwien ac at>
Date: Wed, 12 Dec 2007 15:05:08 +0100


On Wed, Dec 12, 2007 at 12:19:37AM +0100, Diman Todorov wrote:

However, nmap completes the scan without a problem if each host is  
This is interesting since I was able to reproduce the infinite loop by just
running bruteTelnet.nse against my localhost.

nmap -T4 -v -sS -sV -O -n --script=all --script-trace -iL test.lis

ugh, i'll bet the problem is that bruteTelnet.nse never closes the  
ports it opens and the garbage collector never the socket because  
there is always a reference to it.
I just commited a patch to nse_nsock.cc which should fix this issue:
If a second connect() request is issued on an already open socket, the
socket gets closed before the connect is processed. 

This solved the infinite loop with bruteTelnet.nse for me (although the
script took 6 minutes to finish its execution).

It would be great if you could test the patch, before the stable release
gets announced.

I think we'll need to reconsider the open port cap and garbage  
collection policy.


Sent through the nmap-dev mailing list
Archived at http://SecLists.Org

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]