Sorry for the delay. Please see my comments in-line below:
On Wed, 30 Jun 2004, Michel Arboi wrote: > On Wed Jun 30 2004 at 21:34, Jay Jacobson wrote: > > > Could someone provide a description of each of the settings in the new > > global_settings.nasl that was added yesterday? > [snip] > > anti_nessus.nasl and www_fingerprinting_hmap.nasl are enabled by > "Enable experimental scripts" This one sounds good. In the Knowledge Base I will not list specific scripts that are enabled with this option. I assume that over time some other new scripts will be called "experimental" while other experimental scripts will become stable (non-experimental). Correct? Just out of curiousity, what is the criteria that makes a script flagged as experimental? Also, what is the process for an experimental script to become stable? > rh_inetd.nasl launches very slow tests if "Thorough tests" is on. I am familiar with rh_inetd.nasl taking a long time to fully run. However, I think calling the option "thorough tests" may be misleading. Instead, maybe this option should be called "Long-Running Tests" or something like that. Along those same lines, may I recommend that we also include plugin #10927 (blackice_dos.nasl) in this category of long-running scripts. I have frequently witnessed this plugin taking a very long time to run (relative to all the other plugins), not to mention the relatively huge amount of bandwidth this plugin consumes. I will wait to add this option into the Knowledge Base until I hear your thoughts about my concerns with this item. > "Report verbosity" is not used yet but some people complained that > there are too many information in their reports. "Quiet" shoudl fix > this, when it is used. Sounds good. This option currently has three possible states: verbose, normal, and quiet. I understand "quiet" based on your reply, and I understand "normal" would be the same quantity of report information provided today. However, what additional report information might the "verbose" setting provide? If the report verbosity option is not currently in use in any of the plugins and only two verbosity states are clearly understood, maybe this option should only have two states: normal and quiet. Also, the term "quiet" somewhat implies no output. Maybe it should be "minimal" instead of "quiet." Again, I will wait to add this option into the Knowledge Base until I hear your thoughts. > "Log verbosity" and "Debug level" are rather for debugging. > Many scripts have a "debug" variable set to 0 > They should be modified too to help find problems. These two options make sense. I will add them into the Knowledge Base now. ~Jay -- .. .. Jay Jacobson .. Edgeos, Inc. - 480.961.5996 - http://www.edgeos.com .. .. Network Security Auditing and .. Vulnerability Assessment Managed Services .. _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
