On Wed, 18 Dec 2002, Thomas Reinke wrote: > We've noted for a while now that this test is > tripping a LOT of false positives. We're not quite > sure why, other than we note some REALLY odd things > happening if that script gets run manually with > > nasl -t IP iis_webdav_lock_memory_leak.nasl
I noticed this problem earlier this month. It appears to have been introduced between revision 1.11 of the script and 1.11.2.1. Both the version I obtained today with nessus-update-plugins (1.11.2.2) and the one currently in CVS (1.13) are also affected. While I don't know enough about nasl to explain why, I did discover that changing the call to exit() in the function check() to a return() appears to resolve the problem. I did contact the plugin's author as listed in the source ([EMAIL PROTECTED]) and got a response that he no longer uses Nessus and suggested contacting Renaud. I did but have not heard anything back from him. George -- [EMAIL PROTECTED] - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
