Hello Stjepan, On Samstag, 6. Dezember 2008, Stjepan Gros wrote: > with much help/guidelince from Michael Wiegand I wrote change request > towards reorganizing NVTs. There are two goals with this change. One > is to be LSB/FHS compliant, while the other is to enable new features > by NVT reorganization. The feature specifically mentioned is speeding > up load time of openvasd and possiblity to dinamically load (or not to > load) plugins. I would like your feedback on the listed changes and > also any modification or addition required to the list. The CR is > available at, > > <http://www.openvas.org/openvas-cr-24.html>
first thanks for starting to work on this very much desired feature! I have some comments and would be glad if you could consider them for an update of CR#24: * note that there are still some C-plugins (*.nes) in the plugins directory that are platform-dependent. We are working on resolving them, but it will take some time. So, the directory reorganization should consider this in some way. * if you are saying that according to FHS we want the NVTs directory not writable, does this conflict with the aspect that we will have to write new NVTs during a NVT Feed Sync? * last paragraph of rationale: I think this aspect is too ambitious for the moment. Also, we have already a mechanism to switch on/off groups of NVTs: via the detached signatures and trusted signatures. * include_dir: this should allow for a directory structure as well. If you look at http://www.openvas.org/openvas-oids.html there is a special OID space for "Lib" aspired. So, if we associated "iso.org.dod.internet.private.enterprise.OpenVAS" with a special directory, then we have "NVT/lib" as a natural subdirectory where to place inc's and possibly some subdirectories. Another aspect is the search path: will .inc files first searched for in the same directory as the .nasl is? * Design: Yes, I also think that the OID scheme is the best choice to base the dirctory structure on. I propose a careful step-by-step implementation. For example, moving the caching into a separate directory would be a first nice step. There, it could already be realized to have a directory strucure based on the OIDs of the NVTs. All the best Jan -- Dr. Jan-Oliver Wagner | ++49-541-335 08 30 | 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
