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]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

XML output - should <data> be

from [João Vilela] Network Security [Permanent Link]
Subject: XML output - should <data> be
Date: Mon, 23 May 2005 15:34:31 +0100 
Hi!

I'm parsing the nessus xml output to generate custom reports based on that.
Though I'm having a bit of a problem parsing the contents of the "data"
tag because it contains too many different things with no apparent
determined structure. (E.g. "Solution" info comes arbitrarily before and
after the "See also" info.)

Is there any determined structure for the info in the "data" tag that
helps the parsing? Wouldn't it make more sense for that information to
be in their own tags? Since every security note, security warning or
security hole is already delimited by the "information" tag?

E.g.:

(...)
<information>
        <severity> ... </severity>
        <id> ... </id>
        <data> ... </data>
        <solution> ... </solution>
        <riskfactor> ... </riskfactor>
        <cve> ... </cve>
</information>
(...)

Sincerely,
JP
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
[More with this subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Problems with registration feed plugins, Terralink - Supporto Tecnico
Next by Date:  Re: Problems with registration feed plugins, George A. Theall
Previous by Thread:  Problems with registration feed plugins, Terralink - Supporto Tecnico
Next by Thread:  Re: XML output - should <data> be, Drew Simonis
Indexes:  [Date] [Thread] [Top] [All Lists]