[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nmap-dev
Subject:    Re: Follow up to NSE issues -- procedure to reproduce
From:       Patrick Donnelly <batrick () batbytes ! com>
Date:       2009-02-26 18:02:58
Message-ID: 790db3550902261002v7862a542j1c7517978ea6e115 () mail ! gmail ! com
[Download RAW message or body]

Hi David,

On Thu, Feb 26, 2009 at 10:10 AM, David Fifield <david@bamsoftware.com>wrote:

> So now what to do about it? We could store with each script thread a
> list of pending Nsock event IDs, and cancel them all with
> nsock_event_cancel whenever a process is finalized.
>
> David Fifield
>

Well now knowing how to correct the problem, the solution is fairly
straightforward. We can't rely on any sort of gc detection as a user may
save a copy of the thread for some reason. We will need to add a call (to
the nse_nsock) library to perform cleanup on the thread to destroy pending
nsock events.

-- 
-Patrick Donnelly

"One of the lessons of history is that nothing is often a good thing to do
and always a clever thing to say."

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
[prev in list] [next in list] [prev in thread] [next in thread]