Nmap Development mailing list archives
smb-check-vulns.nse:366: calling 'new_socket' on bad self (string expected, got table)
From: Kit Peters <cpeters () ucmo edu>
Date: Wed, 17 Oct 2012 11:30:12 -0500
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. -- - Kit Peters (W0KEH), Engineer II KMOS TV Channel 6 / KTBG 90.9 FM University of Central Missouri http://kmos.org/ | http://ktbg.fm/
Attachment:
nmap conficker scan 17 oct 2012.xml
Description:
_______________________________________________ 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)