On 21 Mar 2002, Michel Arboi wrote:
> Vincent Renardias <[EMAIL PROTECTED]> writes:
>
> > - The find_services.nes plugin timeouts on almost every host I tried it on
> > (even when raising the timeout for this plugin to 10 minutes). Is this a
> > known bug?
I found the source of the problem:
- in find_service.c, the function check_for_socks_proxy() calls the
function open_stream_connection() with the value -2 as timeout parameter.
In this case the function open_stream_connection() sets the timeout to
the default timeout value (20s as set by line 35 of libnessus/network.c).
Since I have many unrecognised services on this machine, there's a 40
second delay for most of them (20 second for each of the 2 calls to
open_stream_connection() in check_for_socks_proxy()), and the 500 seconds
timeout is quickly reached.
For now, I've just hardcoded a much lower timeout for socks autodetection
since I'm unsure of the appropriate way to solve this (and I couldn't get
plug_set_timeout() to do what I wanted to). Maybe let the find_service
timeout be proportionnal to the number of open ports?
Cordialement,
--
Vincent RENARDIAS
Directeur Technique
StrongHoldNET / http://www.strongholdnet.com
