On Wed, Sep 14, 2005 at 10:18:58AM +0200, I am WE4SEL wrote: > Is it possible to set this to > > Ping the remote host[entry]:TCP ping destination port(s) : = built-in, > 1723
No, 'fraid not. > Well ok, this means that the nmap.nasl wrapper is not behaving the way > nmap does, right? Or is nmap doing a TCP ping on its default ports and > this functionality is outsourced to ping_the_remote_host in Nessus? No, it means that ping_host.nasl is defined as a dependency of nmap.nasl. So if you enable dependencies, ping_host.nasl will be run first to ensure the host is alive before wasting time scanning for open ports on a dead host. This can lead to problems if pings fail, as you've uncovered. > Still, then 1723 should probably be added to the built-in ports, right? Straight from ping_host.nasl itself: # H D Moore & Michel Arboi's Port list : # if you want more reliable but slower results, use 'extended' as the port list # 21, 22, 23, 25, 53, 79, 80, 110, 113, 135, 139, 143, 264, 389, 443, 445, # 993, 1454, 1723, 3389, 8080 > Would be nice if nmap and nmap.nasl would act the same, especially for > analysis. I don't know, just my 2 cents... You can always feed Nessus nmap output in grepable format; ie, see "Nmap (NASL wrapper)[file]:File containing grepable results". George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
