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: Changing file formats

Subject: RE: Changing file formats
Date: Tue, 30 Aug 2005 12:09:24 -0400
Risk, Solution, etc. are all arbitrary text inside of the desc field of
individual NASL files.  As far as I can tell there's not even code that
checks to see if that information exists within desc.  It would not be a
simple task to modify Nessus (and all of the nearly 10-thousand individual
NASL plugins) to separate those fields.

PaulM

-----Original Message-----
Subject: Changing file formats

All,
I've long been frustrated by the NBE/NSR format of Nessus reports, and the
XML format isn't much better.  I know I've seen this on the list before, but
is there any way to formalize the structure of the data portion of the
results, such that items like "Risk Factor", "Solution" and "Description"
were individual tokens, as opposed to highly nested (and arbitrarily placed)
elements within the same token?

Is this the sort of thing that can be easily changed via a patch, or is the
format so deeply wound into the product that it is too complicated to
extricate?  


_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>