Jan,
Jan-Oliver Wagner wrote:
Thomas,
On Thursday 15 May 2008 23:30, Thomas Reinke wrote:
Some thoughts we've had:
1) Change the nasl "compiler" to force all variables to be
explictly declared;
2) Default undeclared variables to a local scope;
3) Have a "lint" style checker that examined functions and
warned of global variable usage, which could then be vetted
as acceptable (or not)
Any thoughts?
It would be great if you could prepare a simple NASL script
that demonstrates the danger of the current NASL implementation.
This script could also then serve for debugging and proof it works
better after a change.
Given there really is the weakness you mention (I didn't track down your
hints yet), option 3 seems not really an option to me.
The first option appears as the best solution to me. This should
reduce programming errors.
For option 1 and 2, this would break almost all NASL scripts, and i
don`t go with it, as long no one voluntarily will fix them all .-)
But option 3 is the only one, if you want to be still compatible with
some proprietor security products .-)
Best
Jan
--
Gruss
Lukas Grunwald aka REG lg1
http://www.dn-systems.de mail: [EMAIL PROTECTED]
DN-Systems Enterprise Internet Solutions GmbH
Hornemannstr. 11 31137 Hildesheim, Germany
Tel. +49-5121-28989-0 Fax. +49-5121-28989-11
21 Sunrise Ct, S.San Francisco, CA 94080, USA
Tel. +1-650-472-2512 Mob. +1-650-430-1219
Handelsregister HRB-3213 Amtsgericht Hildesheim
Geschäftsführer Lukas Grunwald
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss