Nmap Development mailing list archives
Re: smb-check-vulns.nse:366: calling 'new_socket' on bad self (string expected, got table)
From: David Fifield <david () bamsoftware com>
Date: Wed, 17 Oct 2012 20:48:41 -0700
On Wed, Oct 17, 2012 at 11:30:12AM -0500, Kit Peters wrote:
Environment: nmap / zenmap 6.01 on windows 7 64-bit, against a Windows XP SP2 host. Expected behavior: script output detailing detected vulnerabilities / infections Actual behavior: error message, "smb-check-vulns.nse:366: calling 'new_socket' on bad self (string expected, got table)" Attached is complete output of nmap run.
Thanks for reporting. I think I found the bug; the code was doing nmap:new_socket() in place of nmap.new_socket() I'm suprised that it ever worked. Maybe the change is because of the new Lua 5.2. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- smb-check-vulns.nse:366: calling 'new_socket' on bad self (string expected, got table) Kit Peters (Oct 17)
- Re: smb-check-vulns.nse:366: calling 'new_socket' on bad self (string expected, got table) David Fifield (Oct 17)