[Openvas-devel] Idea: Detector for silent exit's

Chandrashekhar B bchandra at secpod.com
Wed Apr 15 08:49:01 CEST 2009


-----Original Message-----
From: Jan-Oliver Wagner [mailto:jan-oliver.wagner at intevation.de] 
Sent: Wednesday, April 15, 2009 11:58 AM
To: Chandrashekhar B
Cc: openvas-devel at wald.intevation.org
Subject: Re: [Openvas-devel] Idea: Detector for silent exit's

On Mittwoch, 15. April 2009, Chandrashekhar B wrote:
> > > we have several scripts that do a silent exit() due to some reason.
> > > This makes user believe the NVT ran without identifying a
vulnerability,
> > > though it simply ran across an internal problem and not even tried
> > > to identify anything.
> > > In such cases, at least a log_message() should be applied.
> > 
> > > However, wouldn't it make sense to extend the exit command
> > > with a check whether any report message has been created and
> > > issue a log_message() on its own in case the counter was 0?
> > > (The counter can be increased with any report message command).
> > 
>> Nice idea! We could do this or instead of a counter, we can extend exit()
to
>> accept a optional log string and internally issue a log_message()?

> I was more having in mind to catch all the "exit()'s without telling why".
> If we extend the syntax of exit, then we need to touch all the scripts.

Function arguments can be implemented as optional, so we don't need to touch
the existing scripts.

Chandra. 



More information about the Openvas-devel mailing list