* Stjepan Gros [ 8. Dec 2008]: > > - How will the server admin be able to switch on/off individual > > subdirectories? Should this happen in the server configuration file? > > 1. The simplest way is to restart openvasd. that way it is possible to > comment out specific directories in the configuration file. > 2. Using SIGHUP to reload configuration file, the same as 1 but more dynamic > 3. Via some IPC mechanism that will allow commands to be sent to > openvasd and thus, this is fully dynamic scenario > > A variant of 1 and 2 is to modify openvasd in such a way to load only > plugins that have, e.g. executable bit set. it's easy then to disable > specific plugin by chmod-ing it. > > For a start I would suggest 1. Otherwise we could set too ambitious > goals which have equally high probability of failing. :)
I agree. Setting the directories in the config file is a good start and probably the most intuitive way for server admins. > > - Should the selection be communicated to the client? And if so, in > > which way? > > This requires knowledge and modification of the communication protocol > between the two, which I don't have. So I would suggest also that in > the initial scenario this part is not changed, i.e. client gets a > current list of plugins when it connects to the server. > > In the long term, the answer to this question depends on the uses > cases of openvasd+openvasclient. I don't have enough experience to > make judgements here. This also influences the previous item about > switching on/off specific subdirectories. Maybe success/fail stories > would be useful? Same here; what do the others think? I've talked about this with Felix, we think this would require considerable changes in the client as the client is very conservative regarding its own cache file and will probably get confused by disappearing and reappearing NVTs unless client-side caching is changed as well. > > - You suggested "grammar to include new directives" for the NASL > > subsystem, is this necessary? Should NVTs be aware that they are in a > > different subdirectory? > > No, what I meant was only to introduce three configuration directives > to openvasd.conf that will allow administrator to specify where > plugins are, where global includes are and where to place caches. I > believe there is no point in making NVTs aware of their physical > placement. I understand and agree. :) This should only need relatively minor adjustments afaict from reading openvas-server/openvasd/preferences.c. Any other questions or suggestions regarding Stjepans proposal? Regards, Michael -- Michael Wiegand | OpenPGP key: D7D049EC | 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
