|
Nmap Development
mailing list archives
Re: nmap ends prematurely with a segfault
From: David Fifield <david () bamsoftware com>
Date: Thu, 18 Oct 2007 15:35:23 -0600
On Thu, Oct 18, 2007 at 03:37:17PM -0500, DePriest, Jason R. wrote:
On 10/18/07, David Fifield wrote:
On Thu, Oct 18, 2007 at 03:15:21PM -0500, DePriest, Jason R. wrote:
I run nmap like this:
sudo nmap -v -sSUV -O -pT:-,U:[1-65535] --traceroute --reason
--script=discovery,safe,backdoor,vulnerability,malware --script-trace
-d6 xxx.yyy.zzz.190,153,193,89
and after some time, it eventually ends with a segfault.
Seriously, it ends with a simple "Segmentation fault" and nothing else
to help explain from where the segfault came.
I've been investigating a segfault that I found with --script=discovery.
Do these two commands segfault for you too?
nmap --script=ripeQuery.nse localhost
nmap -6 whois.ripe.net
Do you know of any tests I can for you that wouldn't require my nmap
system to have Internet access?
Sorry, that's all I have for now.
David Fifield
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
By Date
By Thread
Current thread:
|