Nmap Development mailing list archives

Problem/bug in nmap documentation?


From: Anders Thulin <anders () thulin name>
Date: Sat, 22 Sep 2018 11:30:29 +0200

I've discovered what I think is a mis-identification of a service (latest nmap, Linux platform). Nmap does identify a lower-level component used for the service, but not the actual service. (This is not the bug; it's where I started.)

I've searched around, but not found any other recommendation for submitting corrections/additions than that on the 'Community contributions' page (https://nmap.org/book/vscan-community.html), where it says

"Run the command nmap -O -Pn -sSV -T4 -d --version-trace -p<port> <target>, where <port> is the port running the misidentified service on the <target> host."

followed by a pointer to the standard submit page.

However, that command does _not_ produce a service version fingerprint, so there's nothing to submit. (I can only assume it worked at one time, but since has changed no non-working state.) It does provide a os fingerprint, but that's

That's the bug: the command does not work as stated.

Next ... how do I produce the necessary service fingerprint for submission?

regards,
--
/A. Thulin
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/


Current thread: