[Openvas-discuss] Ideas and wishes for future improvements ofOpenVAS

[Kenneth Ng]

Another feature request: a trace function.  Show me sets of queries.
Each query is composed of the rule that was used, the destination IP
and port, the data sent, and the data returned.  This will make it
easier to determine false positives.

On 5/16/07, Robert Rich <rrich at gsti.net> wrote:
> You aren't the only one Kenneth:
>
> http://mail.nessus.org/pipermail/nessus/2004-February/msg00164.html
>
>
>
> -----Original Message-----
> From: openvas-discuss-bounces at wald.intevation.org
> [mailto:openvas-discuss-bounces at wald.intevation.org] On Behalf Of
> Kenneth Ng
> Sent: Wednesday, May 16, 2007 5:01 PM
> To: Jan-Oliver Wagner
> Cc: openvas-discuss at wald.intevation.org
> Subject: Re: [Openvas-discuss] Ideas and wishes for future improvements
> ofOpenVAS
>
> Oh, speaking of client side, have the API between the server and the
> client documented so that different front ends can be put in.  Let
> say, I wanted to call open-vas from Perl, or Python, or whatever.
>
> You want wide eye dreaming?  Build a front end client that will allow
> you to disconnect from the session, and then reconnect later.  Or
> better yet, a client that allows you to disconnect and run background,
> and then can run a arbitrary command (like send email) when the scan
> is complete :-).   And then you run the client again and it reconnect
> right where you left off.  Yeah I'm a dreamer, but you asked :-).
>
> On 5/16/07, Jan-Oliver Wagner <jan-oliver.wagner at intevation.de> wrote:
> > On Wednesday 16 May 2007 21:00, Kenneth Ng wrote:
>
> > > - Ability to do a "diff" between two scan results.
> >
> > A long-standing wish indeed. IMHO this should have high priority.
> > It is a client-side feature though. So maybe to implement in
> NessusClient.
> _______________________________________________
> Openvas-discuss mailing list
> Openvas-discuss at wald.intevation.org
> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
>