Re: Last call before feature freeze in Nessus 1.3.x

I have been working on a new report format that uses a template,
similar to what you mentioned to me before.  The code is almost complete,
there are just a few small bugs to iron out, and some documentation
to do.
As template is parsed through, certain keywords are replaced
with their value.  There are also keywords to control the start
and end of the Hosts, Ports, and Vulnerabilities loop.  Each level
has its own particular keywords that can be used, as well as the
keywords from the levels before it.

Would you and the rest of the Nessus community be interested in
something like this so that you can customize your own reports?
I will hopefully release a rough draft of this soon.

Renaud, the only downside to this is, that a lot of functionality
that I added involves some changes to the client code.  I modified
the backend to parse out the scan times and host scan times, added
about 10 more functions to the report_utils, and I have added an
arglist to store the vulnerabilities by risk level (the original
way of storing them by "warning", "note", and "hole" was left to
maintain backwards compatibility).  I believe that this is more useful
than the original way.
Also, a slight change was made to NTP.  Instead of sending the timestamp
as asctime( localtime( time(...))) or ctime( time(...)), it is sent
across as digits YYYYmmDD HH:MM:SS, so that the tm struct could be
easily rebuilt on the client side (to tell the difference in time).

----------------------
William Heinbockel
Information Security Incident Response Assistant
Co-op Risk & Safety Management
Rochester Institute of Technology
E-mail: [email protected]


On Wed, 12 Feb 2003, Renaud Deraison wrote:

> 
> 
> I'd like to "feature-freeze" the 1.3.x tree really soon (ie: by the end
> of the week), and probably call it Nessus 2.0 (due to all the changes
> that occured internally).
> 
> On my TODO list for this release, I only have to implement a new NASL
> function called "get_kb_list()" which will return an array of KB items
> matching a given expression (ie: get_kb_list("TCP/*") will return all
> the open tcp ports).
> 
> At this stage, everything else will probably be postponed to the next
> release (2.1.x), whose developement will probably start as soon as
> Nessus 2.0 is released.
> 
> My question is : which features are not implemented in 1.3.x yet and
> that you'd like to see implemented before I release Nessus 2.0 ?
> 
> 
> 
> 				  -- Renaud
>