mailing list archives
Re: [NSE] Socket dead-lock
From: Patrick Donnelly <batrick () batbytes com>
Date: Thu, 11 Jul 2013 14:38:27 -0400
On Thu, Jul 11, 2013 at 1:37 PM, <nnposter () users sourceforge net> wrote:
perhaps that passing a socket object from thread to thread is
Even if so, should it result in a dead-lock, as opposed
to an error?
The consequences are undefined.
The script performs password guessing, leveraging brute.lua. It is not
doing any unusual socket work; all it does is connect, read, write, and
close. It maintains a connection pool so that a new connection is not
required for every guess attempt. In the course of the run a connection
may be passed from from one worker to another.
I suggest you setup workers which each manage a single connection.
Sent through the dev mailing list
Archived at http://seclists.org/nmap-dev/