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: NessusClient creates different config files |
|---|---|
| Date: | Thu, 20 Jul 2006 22:24:53 -0400 |
On Thu, Jul 20, 2006 at 02:41:57PM -0500, Scott Pate wrote:
Why would there be two different scanner sets?
The second one is likely the result of NessusClient creating a preference file because one didn't exist when you fired it up. That is, look at preferences_new() in: http://cvsweb.nessus.org/cgi-bin/viewcvs.cgi/NessusClient/nessus/preferences.c?rev=1.7&content-type=text/vnd.viewcvs-markup There's one additional scanner, which would be because that exists on your nessusd host. [The client will add plugins to a config file that exist on the nessusd host but won't remove them.] As for the first, it could be that NessusClient doesn't really "create" a config file. That is, preferences_new() is only called if the file doesn't exist; there's no check on size, though, so if, say, the file exists but is empty, NessusClient would only put those scanners in the file that it finds on the server. 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: segmenation fault erases nessus config file, George A. Theall |
|---|---|
| Next by Date: | Nessus crash: "Empty data string -- closing comm. channel", Melkiades |
| Previous by Thread: | NessusClient creates different config files, Scott Pate |
| Next by Thread: | Nessus 3.0 performance / optimization, r p |
| Indexes: | [Date] [Thread] [Top] [All Lists] |