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: QUICK NESSUS 3.2 QUESTION

Subject: Re: QUICK NESSUS 3.2 QUESTION
Date: Thu, 12 Jun 2008 18:52:00 +0200

On Jun 12, 2008, at 5:26 PM, John Scherff wrote:

Background: We're finally getting around to migrating from 3.06 to 3.2x. Our scanning system is a fairly complex setup comprised of several perl scripts that parse the .nbe output files and load the results into an Oracle database used by a separate, PHP-based web reporting system.

Question: will the new nessus client work with the same command-line switches and will it still produce legacy .nbe output, or must we also migrate to the new .nessus report format? We will eventually re-write our code to use the new format, but prefer to upgrade first and do the re-write later.

Hi John,

Yes, the 'nessus' command line client works as it used it, and still exports as .nbe.


-- Renaud


_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
<Prev in Thread] Current Thread [Next in Thread>