Re: LUA Bug?

[Patrik Karlsson <patrik () cqure net>]

On 30 jan 2011, at 09.38, Michael Pattrick wrote:

> Hello devs,
>
> While playing around with a recent Nmap release I found that scripts
> weren't working for me, see the following command line log. It appears
> to be a problem with the LUA environment variables. The environment is
> a nearly fresh CentOS5 install. I haven't tested this out on other
> platforms but a quick google search reveals at least one other person
> has had problems with this bug (http://pastebin.com/cFXre59L). Any
> ideas?
>
> $ nmap -d9 -A 127.0.0.1
>
> Starting Nmap 5.50 ( http://nmap.org ) at 2011-01-30 03:18 EST
> Fetchfile found /usr/local/share/nmap/nmap-services
> PORTS: Using top 1000 ports found open (TCP:1000, UDP:0, SCTP:0)
> The max # of sockets we are using is: 0
> --------------- Timing report ---------------
>  hostgroups: min 1, max 100000
>  rtt-timeouts: init 1000, min 100, max 10000
>  max-scan-delay: TCP 1000, UDP 1000, SCTP 1000
>  parallelism: min 0, max 0
>  max-retries: 10, host-timeout: 0
>  min-rate: 0, max-rate: 0
> ---------------------------------------------
> Fetchfile found /usr/local/share/nmap/nse_main.lua
> Fetchfile found /usr/local/share/nmap/nselib/
> Fetchfile found /usr/local/share/nmap/scripts/script.db
> ...
> Fetchfile found /usr/local/share/nmap/scripts/ssh-hostkey.nse
> NSE: failed to initialize the script engine:
> /usr/local/share/nmap/nse_main.lua:378:
> /usr/local/share/nmap/scripts/ssh-hostkey.nse:54: variable
> 'SCRIPT_NAME' is not declared
> stack traceback:
>        [C]: in function 'assert'
>        /usr/local/share/nmap/nse_main.lua:378: in function 'new'
>        /usr/local/share/nmap/nse_main.lua:542: in function 'Entry'
>        /usr/local/share/nmap/scripts/script.db:161: in function 'db_closure'
>        /usr/local/share/nmap/nse_main.lua:562: in function 'get_chosen_scripts'
>        /usr/local/share/nmap/nse_main.lua:990: in main chunk
>        [C]: ?
>
> QUITTING!
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/


Hi Michael,

Thanks for reporting this. The bug should only occur when Nmap is compiled without SSL support.
I addressed this bug and another one that showed up after fixing the first one and commited the change as r22114.
You should no longer be seeing this error message and Nmap should properly exclude ssh-hostkey and the scripts relying 
on the wsdd library if no SSL is present.

Regards,
Patrik
--
Patrik Karlsson
http://www.cqure.net
http://www.twitter.com/nevdull77





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