Hello,
I realized that OpenVAS server already has conflict in regard to
the client-server protocol. It sends "NTP/1.1" but
at least one command changed (NESSUS_VERSION->OPENVAS_VERSION)
already.
IMHO we should quickly do the change from the "NTP" to the "OTP" (OpenVAS
Transfer Protocol).
Basically the server should simpy start with "OTP/1.0" and OpenVAS-Client
should be adjusted to know about this as an alternative to NTP.
What we gain is the opportunity to change the protocol
without generating conflicts with Nessus (e.g. we can not invent
our own NTP/1.2 as Nessus might have one of its own).
We loose client tools that are not adapted to "OTP/1.0".
In fact we do not care about proprietary tools, all others
can be patched ;-)
However, are there any other clients be used with OpenVAS
currently? I guess not.
Since it is sort of urgent, I'd like to prepare a change request
for OTP 1.0 with
* NESSUS_VERSION -> OPENVAS_VERSION
* drop ATTACHED_PLUGINS
* add message classes LOG and DEBUG additional to NOTE, INFO, HOLE
Any thoughts appreciated.
Best
Jan
--
Dr. Jan-Oliver Wagner Intevation GmbH, Osnabrück
Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-devel mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
