Hi Geoff, thanks for your thoughts. Please note that we will have alterable tasks in OpenVAS-7 anyway.
On Freitag, 19. April 2013, Geoff Galitz wrote: > I vote for d.1 (part of the target and alterable). > > My reasons: > > - It is a logical portion of the target definition and breaking it out > into it's own config area or even the scan config would feel more > obtrusive. Scan configs are already complex enough. > > - It should be alterable because OpenVAS is used for testing and > operational scans just as much as for compliance audits. In the first two > cases we often need to tune the settings after making a change to our > networks. For audits generally we want to keep things static, but > OpenVAS is used for a lot of operations and research as well, and it > really slows me down and is aggravating to have delete a task or config > just to change a dependent setting. -- Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/ Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 202460 Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
