On Wednesday 08 October 2008 13:39:05 Jan-Oliver Wagner wrote: > On Mittwoch, 8. Oktober 2008, Michael Wiegand wrote: > > I have prepared a change request which should solve the issue with new > > NVTs becoming automatically enabled in OpenVAS-Client in cases where this > > type of behavior is not desirable. > > > > Please take a look at > > http://www.openvas.org/openvas-cr-16.html > > and let me know what you think and whether you agree with this request or > > not. > > > > The change will only happen in the client and should be pretty > > straightforward. > > Basically I vote +1. > > However, you should add extend the CR: > > - the corresponding item on the roadmap cites peridioc execution of the > very same scan. This should be added to Purpose. > > - The Purpose section should also mention, that this is only a first step > towards Family-based scan scenarios. I.e. it should be possible to define a > Family (Debian local security Checks) and have all new NVTs of this family > selected and all others not. > > - Design and Implementation should name the new parameter explicitely, > name the code parts that need to modified. > IIUC from IRC, it makes also sense to add a information dialog about new > NVTs during this change.
Likewise, but as Jan has alluded to, I would recommend some changes to the GUI to accompany the underlying change. Firstly, should there should be an option to enable automatic inclusion of new families. Secondly, if that option is disabled, perhaps the GUI should make some attempt to notify the user that new families exist. I say this, as whilst I see the benefit from an auditing/governance perspective where you may wish to baseline and then measure compliance, from an active testing perspective I want the new plugins and I don't want to forget that they're there. It's probably not a problem for me per se, as I track changes via the commit list but others may choose not to. Cheers, Tim -- Tim Brown <mailto:[EMAIL PROTECTED]> <http://www.nth-dimension.org.uk/> _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
