Hello,
during our improvements to the server and working on OTP[1] and OID[2] stuff
it occured that we would have to invest considerable efford into
additonally supporting NTP and old ID style.
Now that I consolidated the OTP documentation I'd like to make
the protocol more strict (no feature selection - good feature into standard,
bad features out) and thinner (no redundancies, eg. NEW_ATTACK / LONG_ATTACK).
The NTP code is a mess, there is even find knowledge about the syntax
in openvas-libraries :-|
So, what I am planning is to make a big clean up in the trunk versions
of server and client and get all things out we do not need.
Of course the trunk versions should be usable in any state of development.
But it will not be possible to with trunk server and 1.0 client neither
with 1.0 server and trunk client. Oh and trunk client will not work with
any nessus nor will any nessus client work with trunk server.
I am pretty sure we need the big step now, rather than later.
To summarize, the big step would be:
* thin out OTP 1.0
* reduce protocol implementations in openvas-server trunk to only support OTP
1.0.
* strictly use OIDs in openvas-server trunk (there is a legacy method for NASL
scripts with old IDs)
* reduce protocol implementation in openvas-client trunk to only support OTP
1.0
(openvas-client 1.0.x is maintained for NTP support)
* strictly use OIDs in openvas-client trunk.
Any concerns with doing this big step _now_?
Alternatives?
Best
Jan
[1] http://www.openvas.org/openvas-cr-12.html
[2] http://www.openvas.org/openvas-cr-1.html
--
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
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
