Hi!
As described in the document
http://ftp.intevation.de/boss/concept/concept-boss-1.0.1.pdf
there has to be a local storage for tasks and scope (a superset of
the thing formerly known as session).
If there are no compatibility issues, this local storage will be in
XML format.
My question is: Should nessus preferences be kept in these XML
files, too, or should the old .nessusrc be used for this?
As the new GUI should support multiple server connections, the only
way to use the old nessusrc format would be to missuse the sections,
or to introduce something like
nessusd_host = localhost
nessusd_user = foo
nessusd_host[scope1] = the.other.host
ssl_version[scope1] = none
where "scope1" is a scope identifier which shouldn't be the title,
because a title can be text with spaces and special characters and
can be renamed.
XML is not the solution for everything, but in this case it may have
advantages.
What do you think?
Thomas
--
Email: thomas@intevation.de
http://intevation.de/~thomas/
As described in the document
http://ftp.intevation.de/boss/concept/concept-boss-1.0.1.pdf
there has to be a local storage for tasks and scope (a superset of
the thing formerly known as session).
If there are no compatibility issues, this local storage will be in
XML format.
My question is: Should nessus preferences be kept in these XML
files, too, or should the old .nessusrc be used for this?
As the new GUI should support multiple server connections, the only
way to use the old nessusrc format would be to missuse the sections,
or to introduce something like
nessusd_host = localhost
nessusd_user = foo
nessusd_host[scope1] = the.other.host
ssl_version[scope1] = none
where "scope1" is a scope identifier which shouldn't be the title,
because a title can be text with spaces and special characters and
can be renamed.
XML is not the solution for everything, but in this case it may have
advantages.
What do you think?
Thomas
--
Email: thomas@intevation.de
http://intevation.de/~thomas/