Nmap Development mailing list archives
Re: Nmap 4.69beta1 assertion failure
From: David Fifield <david () bamsoftware com>
Date: Sun, 7 Sep 2008 16:17:19 -0600
On Mon, Sep 08, 2008 at 12:05:13AM +0200, LevelZero wrote:
I was poking around on nmap 4.69beta1 today on my XPSP3 box and while doing a basic TCP connect scan, I keep getting assertion failures. I tested both on one of my own boxes and on scanme.nmap.org Below a sample output: nmap -v -v -v -v -d -d -sT scanme.nmap.org <parts cut that run normally> Initiating Connect Scan at 23:53 Scanning scanme.nmap.org (64.13.134.52) [1000 ports] Discovered open port 53/tcp on 64.13.134.52 Discovered open port 80/tcp on 64.13.134.52 Assertion failed: USI->scantype != CONNECT_SCAN, file ..\scan_engine.cc, line 2843
Can you find lines in the output that start with "Changing ping technique"? If so, please send what they say. You need -d2 or -d -d to see them. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Nmap 4.69beta1 assertion failure LevelZero (Sep 07)
- Re: Nmap 4.69beta1 assertion failure David Fifield (Sep 07)
- Re: Nmap 4.69beta1 assertion failure LevelZero (Sep 07)
- Re: Nmap 4.69beta1 assertion failure David Fifield (Sep 08)
- Re: Nmap 4.69beta1 assertion failure LevelZero (Sep 07)
- Re: Nmap 4.69beta1 assertion failure David Fifield (Sep 07)