[Openvas-devel] Dropping NASL_LEVEL
lists at securityspace.com
Mon Apr 6 21:12:00 CEST 2009
Further to my previous email, we have updated our build procedures so
that NASL_LEVEL is no longer being introduced in any new scripts we
Thomas Reinke wrote:
> Jan-Oliver Wagner wrote:
>> 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.
> The only reason we are using it today is that it is still part
> of our script build process. No script that we produce that
> I am aware of is running on any daemon with a low enough script
> level to warrant the conditional lines.
> We'll update our build process to stop producing scripts with
> these levels in them.
More information about the Openvas-devel