Re: non existent script called with --script=all

[Ron <ron () skullsecurity net>]

Oops, that looks like my fault. I probably updated the script db with a 
test script sitting in my folder.

Run:
nmap --script-updatedb

That should fix it.

On a sidenote: would it be possible to print out the changes when 
somebody runs nmap --script-updatedb? That would have made it obvious to 
me that I was adding the wrong script.

Ron

Nelson wrote:
> sudo nmap -v -v -A --script=all -T5 -PN 172.x.x.x
>
> Starting Nmap 4.85BETA8 ( http://nmap.org ) at 2009-04-23 15:47 CDT
> NSE: failed to initialize the script engine:
> /usr/local/share/nmap/nse_main.lua:319: smb-check-vulns-2.nse is not a file!
> stack traceback:
>         [C]: in function 'assert'
>         /usr/local/share/nmap/nse_main.lua:319: in function 'Entry'
>         /usr/local/share/nmap/scripts/script.db:71: in function 'db_closure'
>         /usr/local/share/nmap/nse_main.lua:326: in function 'get_chosen_scripts'
>         /usr/local/share/nmap/nse_main.lua:467: 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

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