Nmap Development mailing list archives
Re: NSE issue with shortport
From: Fyodor <fyodor () insecure org>
Date: Thu, 15 Nov 2007 15:09:15 -0800
On Thu, Nov 15, 2007 at 05:04:53PM -0600, Thomas Buchanan wrote:
I'm not sure the TCP option is needed (can we have a TCP port whose state == PORT_OPENFILTERED ?), but it's included for completeness.
Yes, we can: flog~#nmap -sF -p22 scanme.nmap.org Starting Nmap 4.22SOC7 ( http://insecure.org ) at 2007-11-15 15:08 PST Interesting ports on scanme.nmap.org (205.217.153.62): PORT STATE SERVICE 22/tcp open|filtered ssh Nmap done: 1 IP address (1 host up) scanned in 0.583 seconds Thanks for the patch. Have you tested it very thoroughly? Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- NSE issue with shortport Thomas Buchanan (Nov 13)
- Re: NSE issue with shortport Eddie Bell (Nov 14)
- RE: NSE issue with shortport Thomas Buchanan (Nov 14)
- Re: NSE issue with shortport Eddie Bell (Nov 14)
- RE: NSE issue with shortport Thomas Buchanan (Nov 14)
- <Possible follow-ups>
- RE: NSE issue with shortport Matthew Boyle (Nov 15)
- Re: NSE issue with shortport Fyodor (Nov 15)
- RE: NSE issue with shortport Thomas Buchanan (Nov 15)
- RE: NSE issue with shortport Thomas Buchanan (Nov 15)
- Re: NSE issue with shortport Fyodor (Nov 15)
- RE: NSE issue with shortport Thomas Buchanan (Nov 15)
- Re: NSE issue with shortport Fyodor (Nov 15)
- Re: NSE issue with shortport Eddie Bell (Nov 14)
