
Nmap Development mailing list archives
Re: NSE Socket Operation on a non-socket
From: jah <jah () zadkiel plus com>
Date: Wed, 22 Jul 2009 00:01:58 +0100
On 21/07/2009 20:32, David Fifield wrote:
The error happens when handle_connect_result is called for an SSL connection. At this point the socket's read and write counts are decremented (to zero). Usually after the TCP connection, handle_connect_result needs to be called again to handle an SSL_ERROR_WANT_READ. In this case the read count is incremented (to one). It is normally decremented to zero after that, but in case of a connection timeout it is not. So the socket descriptor remains in the select set and causes the error when selected on.
Nice work!
jah, I bet if you look at your error logs, you will see something like NSOCK (55.7810s) Callback: SSL-CONNECT TIMEOUT for EID 3353 [136.148.92.51:80] near the bottom of the file.
You're right, I do see SSL-CONNECT TIMEOUT right before the error. Cheers, jah _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Re: NSE Socket Operation on a non-socket, (continued)
- Re: NSE Socket Operation on a non-socket David Fifield (Jul 18)
- Re: NSE Socket Operation on a non-socket Joao Correa (Jul 19)
- Re: NSE Socket Operation on a non-socket jah (Jul 19)
- Re: NSE Socket Operation on a non-socket Joao Correa (Jul 21)
- [NSE] - dns.query() return types jah (Jul 21)
- Re: [NSE] - dns.query() return types David Fifield (Jul 21)
- Re: [NSE] - dns.query() return types jah (Jul 22)
- Re: NSE Socket Operation on a non-socket Joao Correa (Jul 19)
- Re: NSE Socket Operation on a non-socket David Fifield (Jul 18)
- Re: NSE Socket Operation on a non-socket jah (Jul 21)
- Re: NSE Socket Operation on a non-socket David Fifield (Jul 21)