[Openvas-discuss] Openvas-client as a nessus client
phantazmm at hotmail.com
Mon Oct 18 23:13:06 CEST 2010
So really I should be concentrating on just getting the Java code to work
with OMP ??
From: "Matthew Mundell" <matthew.mundell at greenbone.net>
Sent: Monday, October 18, 2010 9:42 PM
To: "Derek Sooman" <phantazmm at hotmail.com>
Cc: "Stefano Gargiulo" <rastrano at gmail.com>;
<openvas-discuss at wald.intevation.org>
Subject: Re: [Openvas-discuss] Openvas-client as a nessus client
>> Source code here:
>> If you make any progress please get in touch, phantazmm at hotmail.com , I
>> am trying to adapt this code for my own project but if you manage to do
>> it before me so much the better.
>> It works as is with openvas 1, later versions that use OTP protocol break
>> this, but I think some work to update the code to use OTP or to switch
>> between the two protocols would fix this.
>> I would like to rewrite nessconnect to use Spring Frameworks, etc plus my
>> own Java framework I am writing.
> From an OpenVAS perspective, it would be much more helpful if you wrote
> Java tools and libraries centered around the new protocols. Most probably
> OTP will be stripped right down to a bare minimum in the future. The
> management protocol OMP replaces OTP for end-user clients.
> OMP is described here
> The big changes are that the OMP server controls the scans on the scanner
> and the OMP server stores the scan results in a database. This allows
> clients like web servers to break the connection with the server, and
> removes the need for the client to store the results.
More information about the Openvas-discuss