Nmap Development mailing list archives

Re: NSE: odd output, testing, etc


From: Brandon Enright <bmenrigh () ucsd edu>
Date: Mon, 29 Dec 2008 03:51:00 +0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 28 Dec 2008 20:46:21 -0700 or thereabouts "Patrick Donnelly"
<batrick.donnelly () gmail com> 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.

Brandon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAklYSTAACgkQqaGPzAsl94LaFQCfT7iOfQZ7TRzVik/1H09J0yQi
oNcAnjDyl78USGvEaWPLfqE2ORbZevvy
=NVfy
-----END PGP SIGNATURE-----

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


Current thread: