Nmap Development mailing list archives

Re: NSE: odd output, testing, etc


From: David Fifield <david () bamsoftware com>
Date: Sun, 28 Dec 2008 21:07:41 -0700

On Mon, Dec 29, 2008 at 03:51:00AM +0000, Brandon Enright wrote:
On Sun, Dec 28, 2008 at 6:34 PM, David Fifield
<david () bamsoftware com> wrote:
So it sounds like the scripts are running and blocking fine. The
only problem is that they tend to time out before they get a chance
to do anything. Brandon said that after one round of scanning with
more than 300 script threads running, in the next round NSE locks
immediately. Could something about timing out scripts be corrupting
the Lua state? The problem goes away when r11122 is reverted. That
was the change that made use of a persistent Lua state.

I need more information than NSE locking up on the second scan to
determine the cause. As far as I know Brandon hasn't had this problem
anymore after I corrected the threads improperly finishing because of
time outs.

Reverting r11122 kept the problem from propagating to later NSE scans
but as Patrick mentioned, properly handling thread timeouts completely
eliminated the problem.

Good news, and well done Patrick. What revision fixed the timeout
problem? Was it r11499? The only other thing I can think of is
http://seclists.org/nmap-dev/2008/q4/0727.html, but that wasn't
committed.

David Fifield

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


Current thread: