Mailing List Archive

XML 1.3.0
In XML generated by 1.3.0 there are plugin elements, which have an id that
is referenced in the results. This id, is it something that is made up per
report or is a globally referencable number that will "never" change.
Basically, I am trying to determine whether I want to have a new set of
data stuffed into the table for the plugins used in each report or if
"batch" imports of plugin data would be acceptable.
Matt

--
Matt Woodyard - CISSP
Connecting hackers to your information.
Now that's 1 degrees of separation.
Re: XML 1.3.0 [ In reply to ]
On Thu, Oct 31, 2002 at 06:07:27PM -0500, Matt Woodyard wrote:
> In XML generated by 1.3.0 there are plugin elements, which have an id that
> is referenced in the results. This id, is it something that is made up per
> report or is a globally referencable number that will "never" change.
> Basically, I am trying to determine whether I want to have a new set of
> data stuffed into the table for the plugins used in each report or if
> "batch" imports of plugin data would be acceptable.

If you are referring to XML version 1.3.0 then I think the id is global
(it is the actual nessus plugin id). When I do my XML imports, I ignore
the plugins section at the top of the XML document and simply fetch the plugin
information once (for insertion into a db) via:

nessus -qSp localhost 1241 login password > out.sql

Rohan