[Openvas-devel] Fwd: Dropping NASL_LEVEL

Tim Brown timb at nth-dimension.org.uk
Mon Apr 6 16:58:17 CEST 2009

Cross posted to openvas-plugins as it makes more sense to ask the question 

My personal view is that we should start cleaning out the legacy code from the 
scripts where we can do so safely, this is a good example of something that 
can easily be retired.

----------  Forwarded Message  ----------

Subject: [Openvas-devel] Dropping NASL_LEVEL
Date: Monday 06 April 2009
From: "Jan-Oliver Wagner" <jan-oliver.wagner at intevation.de>
To: openvas-devel at wald.intevation.org


I wonder whether we should simply drop NASL_LEVEL entirely.
Which in fact means that all the if-clauses used in .nasl-skripts
can be resolved.

OpenVAS started with a level 2300. Also we introduced
OPENVAS_NASL_LEVEL because we do not want to mix
up with Nessus. 
So, for OpenVAS users the NASL_LEVEL conditionals are
always true anyway.

I guess, this primarily concerns those who try to keep
NASL-Skripts compatible with Nessus. Any opinion from your side
on this idea to drop the NASL_LEVEL.
Would it cause problems?

Why not keep NASL_LEVEL? Well, it is confusing to new users, comsumes
code lines and adds to complexity of some scripts.



Dr. Jan-Oliver Wagner | ++49-541-335083-0  |  http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
Openvas-devel mailing list
Openvas-devel at wald.intevation.org


Tim Brown
<mailto:timb at nth-dimension.org.uk>

More information about the Openvas-devel mailing list