Nmap Development mailing list archives
Re: [PATCH] Additional information when using --version-trace
From: David Fifield <david () bamsoftware com>
Date: Mon, 8 Jun 2009 17:44:19 -0600
On Thu, Jun 04, 2009 at 07:49:07PM -0500, Tom Sellers wrote:
When doing service version detection work I sometimes run into a problem where I am not sure which probe was just sent and when or what match lines are being triggered. This doesn't happen often, but when it does it presents quite a problem. The recent Oracle fingerprint was an example of this. Normally, if I cannot read the data at the end of the Write request line I just have to guess as to which probe was just sent and on what protocol. I have attached a patch that displays additional information when --version-trace is used.
Thanks, Tom. I merged the patch with a couple of small changes: probe announcements are sent to LOG_PLAIN, not just LOG_STDOUT; and they get printed with -d2 as well as --version-trace (as some other messages are). David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- [PATCH] Additional information when using --version-trace Tom Sellers (Jun 04)
- Re: [PATCH] Additional information when using --version-trace David Fifield (Jun 08)