Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




nmap-dev logo Nmap Development mailing list archives

Re: nmap+V
From: "Paul Tod Rieger" <prie () abl com>
Date: Thu, 24 Aug 2000 09:45:41 -0400

Fyodor <fyodor () insecure org> wrote:

This is exactly why I am not sure that adding version # detection is
worthwhile.  People won't be satisfied with simple version numbers!  As
you say, they always want to probe for more info.  This is why I am
considering ONLY worrying about service protocol detection while leaving
version + application specific probes to modules that run later (or
another program entirely).

If nmap goes to the trouble of collecting banners to detect protocols, I'd
hate to throw out that info.  Maybe there could be a "verbose" option, so
the user could either:

# nmap -sS -doubleCheckProtocol
[does the above]

or

# nmap -sS -doubleCheckProtocol -printBanners
[above plus a separate listing of the banner at each port (separate like the
OS-detection info) and the result of the "GET"]

Tod
abl.com



---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to 
nmap-dev-help () insecure org . List run by ezmlm-idx (www.ezmlm.org).



  By Date           By Thread  

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