Hi, in a project I am using OTP for manipulating the communication between OpenVAS-Scanner and OpenVAS-Manager for viewing the effects of the tests and effects of CRT on embedded devices.
-Have you implemented OTP with your own programming language and tools or have you used API elements of openvas-libraries/openvas-scanner for this? -> The OTP-commands are parsed inside my tool without the help of the OpenVAS-API. - Which of the OTP commands did you implement? -> Because I am manipulating the communication it's almost all commands. -Which OTP commands do you really need in the future and which could you drop? -> The communication is effected, so I think all are needed. -Is OTP critical for your activities/processes? -> Yes ;-) -Is OMP an alternative for your OTP use case? -> Doesn't OMP has another function than OTP? In the protocol documentation you say that eventually OTP will be replaced by OSP and not by OMP. Or will you change the way the scanner and the manager are used? I didn't have a look at OMP until now. But if the communication between scanner and manager stays the same, the problem would just be some days coding. But this discussion is interesting. What changes will there be with the changing of the protocols? Jan-Christopher Brand
_______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
