> http://sourceforge.net/projects/nessconnect/
>
> Source code here:
>
> http://sourceforge.net/projects/nessconnect/files/Nessconnect%20%28current%29/1.0.2/nessconnect-1.0.2-src.zip/download
>
> If you make any progress please get in touch, [email protected] , 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
http://www.openvas.org/openvas-cr-28.html
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.
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
