Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: significance of ping_host in nessusrc |
|---|---|
| Date: | Wed, 19 Jul 2006 07:23:53 -0400 |
On Tue, Jul 18, 2006 at 08:12:21AM -0500, Scott Pate wrote:
I am not sure if this problem is new to the 3.x version, as I don't remember having it in the past, but I have recently been forced to use the GUI for running nessus, as I don't seem to get consistent results by editing .nessurc and running in batch mode (which I would very much prefer to do) I'm running nessus 3.0.1 on Fedora core 4 using NessusClient,
...
After some investigation, I learned that 'ping_host' seems to have no effect, and it is the actual plugin in the .nessurc file which determines whether the host is ping'd.
Yes, ping_hosts is a deprecated feature of NessusClient.
Ping the remote host[entry]:TCP ping destination port(s) : = 1-3000 Ping the remote host[checkbox]:Do a TCP ping = no 11219 = yes nessus scans the port range 1-3000.
This is probably because you're implicitly enabling #10180 (ping_host.nasl) through the #11219 (the SYN Scan plugin). Also, note that the port(s) to TCP ping (as opposed to the port range to scan) should be specified either as a series, with semicolons separating the actual numbers, or the word "built-in" or "extended".
Ping the remote host[entry]:TCP ping destination port(s) : = 1-3000 Ping the remote host[checkbox]:Do a TCP ping = yes 11219 = no only first digit is recognized in port range (port 1)
Do you have other port scanners enabled? Also, the port range is specified incorrectly (see above).
Ping the remote host[checkbox]:Do a TCP ping = no 10180 = yes 11219 = no ping_host.nasl runs, and then plugins start to run as well, even though there was no response from ping.
ping_host.nasl runs because you've enabled it explicitly. I'm not sure what the settings for the other ping-related options are, or even that of unscanned_closed.
I there documentation on the sections of the config file, and the implications of the settings contained within
Have you seen the Nessus Knowledge Base that edgeos maintains? It's at: http://www.edgeos.com/nessuskb/ George -- theall@tenablesecurity.com _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Problem Running the Nessus Client, George A. Theall |
|---|---|
| Next by Date: | Local checks on AIX (and Solaris), PaJohnston |
| Previous by Thread: | significance of ping_host in nessusrc, Scott Pate |
| Next by Thread: | Re: Problem Running the Nessus Client, George A. Theall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |