Author: mwiegand Date: 2008-10-08 16:17:43 +0200 (Wed, 08 Oct 2008) New Revision: 1496
Modified: trunk/doc/website/openvas-cr-16.htm4 Log: Made CR #16 more clear based on Jan-Olivers suggestions on openvas-devel. Modified: trunk/doc/website/openvas-cr-16.htm4 =================================================================== --- trunk/doc/website/openvas-cr-16.htm4 2008-10-08 12:44:20 UTC (rev 1495) +++ trunk/doc/website/openvas-cr-16.htm4 2008-10-08 14:17:43 UTC (rev 1496) @@ -34,9 +34,16 @@ <p> To make the behavior of OpenVAS-Client more flexible and more useful for - scanning with fixed NVT sets. + periodic scanning with fixed NVT sets. </p> +<p> + To make a first step towards family-based scan scenarios. In the future it + should be possible to define a family (like Debian local security checks) and + automatically enable all new NVTs of this family, while new NVTs from other + families stay disabled. +</p> + <h3>References</h3> <p> @@ -58,6 +65,12 @@ enabled has to manually disable all new NVTs after connecting to the server. </p> +<p> + As stated under <i>Purpose</i>, this scheme is intended to allow for + family-specific settings at a later date; there are cases where new NVTs of a + specific family should be enabled, but other new NVTs should not. +</p> + <h3>Effects</h3> <p> @@ -73,6 +86,10 @@ plugin selection section of OpenVAS-Client and will be scope-specific. </p> +<p> + The automatic enabling of NVTs happens in nessus/context.c (context_add_plugin). + This would probably a good place to check for the value of the new preference. +</p> <h3>History</h3> _______________________________________________ Openvas-commits mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-commits
