On Monday 19 May 2008 01:49, Thomas Reinke wrote:
> $ nasl -v
> nasl 2.2.5
>
> Copyright (C) 2002 - 2004 Tenable Network Security
>
> See the license for details
>
> $ ./test.nasl
> ** WARNING : packet forgery will not work
> ** as NASL is not running as root
> 1
> 5

same with openvas-nasl :

$ ./openvas-nasl -X /tmp/testme.nasl
** WARNING : packet forgery will not work
** as NASL is not running as root
1
5

And same with nasl 2.2.8.

> Both of these results demonstrate quite clearly how the author of
> a function "testme" can use a variable "x" that has no explicit
> declarations, intend the variable to be local, yet have consequences
> that the caller's scope is used.  All of the previous examples
> I cited were examples of this problem.  In many cases, it was
> obvious that authors _attempted_ to avoid the problem by using
> "local_var" constructs.  But since they in many cases forgot
> to do so, or missed one or more variables, the problem persists.
>
> Perhaps Tenable has gone ahead and corrected the scripts themselves
> to avoid this situation.  It does not, address the root problem,
> which through inheritance, OpenVAS has in the daemon.
>
> If I'm wrong, _constructive_ criticism is more than welcome.
> But, unless I misunderstand when NASL2 was released, I don't
> think I've made a mistake here.

I am convinced this is a design flaw in NASL and that we
should fix this in OpenVAS regardless whether there were
changes to Nessus meanwhile or not.

Best

        Jan
-- 
Dr. Jan-Oliver Wagner                                   Intevation GmbH
Amtsgericht Osnabrück, HR B 18998             http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to