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.
Best
Jan
--
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
