Michael Schmitt <[EMAIL PROTECTED]> writes:
> english {
> name = "blablabla";
> desc = "foobar";
> }
This means that the NASL syntax has to be changed, which creates a
portability problem with old Nessus.
We'll probably have to do it, at the next major release maybe, but
we'll have to think about everything we need in NASL++
> 3. Are statement such as
> "script_description(english:desc["english"]);" really needed? We don't
> think so.
Maybe the interface could be changed to a simple variable affectation,
right.
> script_family(english:"Misc.", francais:"Divers");
> A little typo in the french name and you get two families!
That's not a big problem, and is usually quickly detected.
> family names should happen at a central place outside the plugins
Maybe we should also change the system and allow a plugin to be a
member of several families
(e.g. an attack against IIS that gives an admin shell could be in
something like "remote root access", "windows" and "www")
> Type of attack on the first level, type of OS on the second, ...)
A multilevel family system might be interesting too.
> We believe that at least some of these proposals could be realized
> without major code changes
But there is a compatibility problem with old versions.
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
