Nmap Development mailing list archives
Re: Strange beahviour/bug with nmap rpc-grind script
From: David Fifield <david () bamsoftware com>
Date: Wed, 19 Jun 2013 16:57:25 -0700
On Tue, May 28, 2013 at 10:23:57AM +0200, Luca Filippi wrote:
I am having problems with an UDP scan with nmap from SVN which I compiled two days ago. This is my command line: nmap -sU -sV -iL reti.txt -oA reti-udp_selected_ports_da_ip_10.55.81.105_NAC_guest_PN_sV --reason -v -v -PN --min-rate=250 --max-rtt-timeout=50ms --max-retries=2 -n --min-hostgroup=2048 --min-parallelism=4000 --script-args 'rpc-grind.threads=200' -p161,111,135,137,138,139,1434,500,53,69,445 First of all, the scan takes ages to complete. RPC-grind is automatically select because of the -sV flag.
Thanks for this report. I was not able to reproduce it, however that doesn't necessarily mean anything. I found that a bug in rpc-grind prevented a proper error message from being shown, and I think the error message might help find the cause of the problem. The message NSE: rpc-grind ReceivePacket(): nil should have a real error message in place of "nil". I committed a fix for this in r31010, and I've also attached a patch. Can you please try it, and see what the error message says? Do you happen to know the actual server version that's running on port 111 on these targets? David Fifield
Attachment:
rpc-grind-ReceivePacket.patch
Description:
_______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Strange beahviour/bug with nmap rpc-grind script Luca Filippi (May 30)
- Re: Strange beahviour/bug with nmap rpc-grind script David Fifield (Jun 19)