On Mon, May 23, 2005 at 10:39:34AM -0700, John Harris wrote: > Unfortunately for us, the tcp_seq_window.nasl test still > returns the odd key "TCP/seq_window_flaw is missing" > message.
I think you mean to say that tcp_seq_window.nasl is failing to set this particular key. Plugins that have this as a dependency might return this message, but not tcp_seq_window.nasl itself. > So are there any other reasons this "key" shows up here as > not obtainable? There are a variety of reasons why it might not be set. To find out what's happening for your scans, your best option is to enable debugging and watch for messages in nessusd.dump. For this script, you enable debugging output by editing the script and set the variable debug to 1 instead of 0. George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
