On Donnerstag, 19. Februar 2009, Stjepan Gros wrote:
> Well, after patch for plugins has been integrated, I suppose I could try
> to do something else. There are three possibilities:
>
> 1. there are places where word nessus is still mentioned (licenses
> excluded). this should be relatively easily to change and it would be a
> short term task
I prefer to have this done for the next major release.
There are many function names etc. that contain "nessus".
Renaming them would mean to break API.
So, probably it is better to begin the tabula rasa after the 2.0 series is
branched and trunk heading for 3.0.
> 2. i could start with IPv6 implementation. this is a longer term task
> and it would require first that we agree on how to abstract IPv4/IPv6
> specific code from the majority of the openvas
That'll be a good new feature. You could start with further analysis and
first small patches (please keep them as small at possible ;-).
> 3. starting to phase out openvas internal implementation of basic
> algorithms and data structures and replace them with glib's structures.
> this is the most complex task of the three.
I am moving my mind here and have the idea to start another
library inside openvas-libraries: "libopenvascommon".
My hope is to have a sample and RFC within the next weeks.
However, other aspects come immediatley to my mind that
could be done independent of larger strategies:
For example
* use the glib ini-file API for all .conf files.
* have timestamps for the openvasd.dump file
> I could start with 1, as it is the easiest task. Is that ok?
Most intersting/challenging is probably 2.
3 allows for some simpler, "programming" tasks.
1 should be postponed.
Of course we like to have all of them to be worked on :-)
Best
Jan
--
Dr. Jan-Oliver Wagner | ++49-541-335083-0 | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
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
