No doubt there are more efficient ways of handling this. (You have
to remember though, a given test may include checks for multiple
releases.)
One could, however, wrapper within the main body of the lsc
all checks for a given release in an if-then block so that it
was only executed if the host was identified running that
release.
Better yet (and probably easier to do, and somewhat more clean while
limiting changes), would be to tag a given distribution's LSCs with
a unique kb entry (a simple boolean, within gather-package-list.nasl)
and make the entire script have a
"script_require_keys('<boolean kb entry');", thus ensuring
that the daemon won't even launch the script if the distribution
doesn't match. (Now that I think of it, I'm embarassed that we
didn't do that earlier.)
Given the nature of the automated code generation, this would be
simple and probably get the biggest performance gain as the
daemon would take care of not bothering to launch the majority
of LSC's for any given host.
Thomas
Jan-Oliver Wagner wrote:
> Hi,
>
> the method "isdpkgvuln" is typically used several times by a local
security check.
> In case "ssh/login/release" is not the one seeking for, shouldn't it
be possible to avoid further tests on this?
>
> Best
>
> Jan
_______________________________________________
Openvas-plugins mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-plugins
