On Freitag, 19. März 2010, Hartmut Goebel wrote: > Am 19.03.2010 09:11, schrieb Jan-Oliver Wagner: > > What is missing yet is a completed documentation of the OMP protocol > > so that you know about any actions to apply via omp-cli. > > I played around with OMP a few days now (and implemented a Python OMP > client library). From my point of view, OMP is inconsistent and not well > designed. I know, there is already quite some software around using OMP > as it is now. So use it this comment as "lessons learned". > > Here are some examples:
OMP is not finalized yet. It is a open-for-discussion Change Request (http://www.openvas.org/openvas-cr-28.html). In fact a final protocol cleanup phase is still due and on our roadmap. Thats why openvas-manager, gsa, etc. is still in beta. So, thanks for the examples. Some of them were already on our todo list. It is good to have further OMP client developers to share thoughts! However, the examples only tackle what I call minor design issues. If you look at OTP (not much different from the Nessus protocol NTP) then you can see really significant design flaws which we hope to have solved (mostly) with OMP. Best Jan -- Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/ Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 202460 Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
