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.




Network Security Nessus-Users
[Top] [All Lists]

Re: Recreate nessusrc files when updating nessus?

Subject: Re: Recreate nessusrc files when updating nessus?
Date: Fri, 13 Apr 2007 21:02:34 -0400
On 04/12/07 03:32, Max Andersen wrote:

I just scanned 2 AIX servers with nessus 3.0.4 and the latest plugins. The systems reported are with security holes, since plugin 14611 reports that the maintenance level of the AIX servers are 3, and the latest available is 4.

The report then states that a newer nessus is available. I then install 3.0.5 and get the latest plugins available, and the report now shows nothing about 14611.

Do I have to recreate all nessurc files I use in batch when upgrading nessus, or am I missing something?

No, you don't need to recreate them. Have you looked at the nessusd.messages logfile for the second scan to see whether aix_maintenance_level.nasl was actually run?


Btw, the description for the plugin was changed on April 6th (Revision 1.10). Is it possible you're looking for specific text from the old version of the plugin?

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>