Re: [NSE] nmap timing info for scripts

["Eddie Bell" <ejlbell () gmail com>]

On 10/01/2008, Thomas Buchanan <TBuchanan () thecompassgrp net> wrote:
> This seems like a good idea to me.  Another thought I had regarding
> timing was the ability to wait between socket connect attempts.  Lua
> doesn't seem to have a built-in sleep() function, as far as I can tell.
> Would there be value in adding something like that to the nmap NSE
> library?
>
> Thomas

Yeah (maybe if you had a script that needed it?), it shouldn't be too
hard If you use the nse bitlib as a guide.

My only concern is that usleep will block so will waste time when
other scripts could be running . Perhaps there is a more efficient
non-blocking way to achieve the same thing (continuation 'yield'
style). I don't really know enough about nse internals though.

On 10/01/2008, Matthew Boyle <matt_boyle32 () hotmail com> wrote:
> wouldn't it be better just to set the timeout to something appropriate for
> the timing options (rather than the fixed DEFAULT_TIMEOUT we have at the
> moment) when the socket is created?  maybe it could even be based on the
> host's current timeout thresholds.

I don't think we will have access to the correct data structures to
use the current threshold. Setting a different default timeout based
on the timing level is also a option. It depends if we want to
guarantee a constant 'start state' for scripts. If we use something
like the function above it is up to the programmer to set a timing
level based timeout instead of nmap.

I think we should, at least, include thomas's patch

anyone else?
 - eddie

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