If you are using the WX client, there is a way to remove this information before generating the report or data export.
Regards, Sonny Discini, Senior Network Security Engineer Department of Technology Services Enterprise Infrastructure Division Montgomery County Government -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jay Jacobson Sent: Monday, December 06, 2004 11:15 AM To: Anubis Tut Cc: [EMAIL PROTECTED] Subject: Re: No reporting of dependencies? On Mon, 6 Dec 2004, Anubis Tut wrote: > All, > > Is there a way to scan, with dependencies enabled, that will not > report on these dependencies? I am only concerned about the > dependencies insomuch as they allow the specific plugin to be > executed, I am not concerned with their results. I do not believe there is a way built-into Nessus to do what you are looking for. However, it should not be tough to accomplish this. Since you are parsing the scan results with some script, I presume you are generating the results in NBE (or maybe XML) format. Solution: Simply 'grep' the NBE output file for the plugin ID# you want. Done. :) ~Jay -- .. .. Jay Jacobson .. Edgeos, Inc. - 480.961.5996 - http://www.edgeos.com .. .. Network Security Auditing and .. Vulnerability Assessment Managed Services .. _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
