Nmap Development mailing list archives
Re: Limits for qscan
From: David Fifield <david () bamsoftware com>
Date: Wed, 18 Aug 2010 17:37:58 -0600
On Wed, Aug 18, 2010 at 06:23:51PM -0400, Matt Selsky wrote:
On Wed, 18 Aug 2010, Ron wrote:Feel free to test against skullsecurity.org. I should have lots of open ports in the 1-1024 range, many of which go to different servers (22, 23, and 24 are all ssh to different boxes).Using latest svn: $ ./nmap --datadir=. -p22-24,80 --script qscan --script-args qscan.confidence=0.95,qscan.delay=200ms,qscan.numtrips=10 skullsecurity.org Starting Nmap 5.35DC18 ( http://nmap.org ) at 2010-08-18 18:13 EDT Nmap scan report for skullsecurity.org (206.220.193.152) Host is up (0.065s latency). rDNS record for 206.220.193.152: dhcp-ip-152.biz2.winnipeg.voinetworks.net PORT STATE SERVICE 22/tcp open ssh 23/tcp open telnet 24/tcp filtered priv-mail 80/tcp open http Host script results: | qscan: | PORT FAMILY MEAN (us) STDDEV LOSS (%) | 22 0 0.00 -0.00 100.0% | 23 1 0.00 -0.00 100.0% |_80 2 0.00 -0.00 100.0% Nmap done: 1 IP address (1 host up) scanned in 11.73 seconds I'm scanning from OSX on a wireless connection. Am I doing something wrong?
This is probably the bug that pcap reads don't work on OS X right now, which I'm looking into. 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:
- Limits for qscan David Fifield (Aug 12)
- Re: Limits for qscan Tom Sellers (Aug 17)
- Re: Limits for qscan Ron (Aug 18)
- Re: Limits for qscan Matt Selsky (Aug 18)
- Re: Limits for qscan David Fifield (Aug 18)
- Re: Limits for qscan Ron (Aug 18)
- Re: Limits for qscan Tom Sellers (Aug 17)