Nmap Development: Re: Missing XML scaninfo entity for ping scan

[Fyodor <fyodor () insecure org>]

On Fri, Jan 07, 2005 at 12:12:57PM -0000, Martin O'Neal wrote:
> When running a ping scan (echo, mask, timestamp) and nothing else, the
> scaninfo xml entity doesn't get included, so you have no idea (without
> analysing the args in the nmaprun entity) what the scan was.
>
> Can the scaninfo entity be included for all scanning?
The scaninfo element is printed once for each type of port scan
conducted.  So you get two of them if you do a SYN and UDP scan, each
of which tells what ports the respective scan is testing.  A ping-only
scan does not print any scaninfo lines, because that doesn't really
count as a port scanning technique.  Perhaps there should be a
pinginfo line, breaking down what types of pings were used.  I suspect
a lot of people would like to see the ping results in that element as
well.  Nmap currently does not tell which ping types elicited a
response unless you use --packet_trace.

Cheers,
Fyodor

---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to 
nmap-dev-help () insecure org . List archive: http://seclists.org