Home page logo
/

nmap-dev logo Nmap Development mailing list archives

RE: NSE issue with shortport
From: "Thomas Buchanan" <TBuchanan () thecompassgrp net>
Date: Thu, 15 Nov 2007 17:15:26 -0600

No, I wouldn't say thoroughly.  I checked to see that it correctly
worked against an open|filtered UDP port.  My testing box is Linux, so
haven't compiled/checked on Windows, etc.

Thomas

ps.  Just checked the TCP example you gave:

# nmap -sF --reason -v -p 22 scanme.nmap.org
PORT   STATE         SERVICE REASON
22/tcp open|filtered ssh     no-response

# nmap -sFV --reason -v -p 22 scanme.nmap.org
PORT   STATE SERVICE REASON       VERSION
22/tcp open  ssh     tcp-response OpenSSH 4.3 (protocol 2.0)


-----Original Message-----
From: Fyodor [mailto:fyodor () insecure org] 
Sent: Thursday, November 15, 2007 5:09 PM
To: Thomas Buchanan
Cc: Matthew Boyle; nmap-dev () insecure org
Subject: Re: NSE issue with shortport

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


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault