Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Nessus: devel

NASL2 reference manual

 

 

Nessus devel RSS feed   Index | Next | Previous | View Threaded


arboi at noos

Feb 4, 2003, 7:06 PM

Post #1 of 6 (266 views)
Permalink
NASL2 reference manual

Any comment on this?
It is far from finished, (and I already know that I triggered some bugs
in Lyx with the funny >> and >>> operators)


arboi at noos

Feb 4, 2003, 1:15 PM

Post #2 of 6 (263 views)
Permalink
Re: NASL2 reference manual [In reply to]

> Any comment on this?

Better with an URL, I suppose :-(
http://mapage.noos.fr/arboi/nasl2_reference/

The Lyx source is in the CVS repository...


rich at westpoint

Feb 5, 2003, 7:40 AM

Post #3 of 6 (265 views)
Permalink
Re: NASL2 reference manual [In reply to]

This basically looks good to me so far, but I do have a couple of comments:

http://mapage.noos.fr/arboi/nasl2_reference/node32.html

I notice that the progress function (scanner_status) is specific to
scanners and cannot be used by other types of plugin. How about making
it into a more generic function eg. plugin_status so that plugins which
can take a long time (such as the web mirroring script) can also make
use of it. The meaning of the two arguments would have to change to be
the amount of work done and the total amount rather than refering
specifically to ports.

Another related idea is having a heartbeat function which would allow a
plugin to remind the system that it is alive. This even could be used in
combination with the timeout stuff perhaps (maybe temporarily supressing
it).

Cheers

Rich.


arboi at noos

Feb 5, 2003, 2:21 PM

Post #4 of 6 (264 views)
Permalink
Re: NASL2 reference manual [In reply to]

Richard Moore <rich [at] westpoint> writes:

> I notice that the progress function (scanner_status) is specific to
> scanners and cannot be used by other types of plugin. How about making
> it into a more generic function eg. plugin_status so that plugins
> which can take a long time (such as the web mirroring script) can also
> make use of it.

Well, 1st, a scanner can say "I have done 55% of the port range", most
plugins (like webmirror.nasl) cannot. 2nd, sooner or later, the
"current" plugin name will not be displayed any more, because it is
not "current" and there is no simple way it can be.

> Another related idea is having a heartbeat function which would allow
> a plugin to remind the system that it is alive. This even could be
> used in combination with the timeout stuff perhaps (maybe temporarily
> supressing it).

A well designed plugin should not need it. And a badly designed plugin
with keep saying "I'm working! I'm working!".
What's the difference with a big timeout?


rich at westpoint

Feb 6, 2003, 9:18 AM

Post #5 of 6 (263 views)
Permalink
Re: NASL2 reference manual [In reply to]

Michel Arboi wrote:
> Richard Moore <rich [at] westpoint> writes:
>
>
>>I notice that the progress function (scanner_status) is specific to
>>scanners and cannot be used by other types of plugin. How about making
>>it into a more generic function eg. plugin_status so that plugins
>>which can take a long time (such as the web mirroring script) can also
>>make use of it.
>
>
> Well, 1st, a scanner can say "I have done 55% of the port range", most
> plugins (like webmirror.nasl) cannot. 2nd, sooner or later, the
> "current" plugin name will not be displayed any more, because it is
> not "current" and there is no simple way it can be.
>

I would have thought the webmirror plugin could do this because it knows
how many documents it is allowed to fetch, I'm sure there are other
possible plugins that this could be true of. Either way, it was just a
suggestion.

>
>>Another related idea is having a heartbeat function which would allow
>>a plugin to remind the system that it is alive. This even could be
>>used in combination with the timeout stuff perhaps (maybe temporarily
>>supressing it).
>
>
> A well designed plugin should not need it. And a badly designed plugin
> with keep saying "I'm working! I'm working!".
> What's the difference with a big timeout?
>

Well, I'm thinking about what happens when you are scanning machines on
very slow networks. I take the points you make though, and perhaps it
isn't worthwhile.

Cheers

Rich.


arboi at noos

Feb 6, 2003, 4:05 PM

Post #6 of 6 (269 views)
Permalink
Re: NASL2 reference manual [In reply to]

On Thu, 2003-02-06 at 11:18, Richard Moore wrote:
> I would have thought the webmirror plugin could do this because it knows
> how many documents it is allowed to fetch

Actually, we limited webmirror.nasl because it is very slow. IMHO it
should be rewritten in NASL2 and enhanced (e.g. with eregmatch)

Nessus devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.