Hi there We have a home-written NASL. It was written, successfully tested using "nasl -t ...." and then nessusd was restarted. A scan was run and the NASL successfully ran.
Yesterday, I made some big changes in it, tested it successfully using "nasl -t..." and then restarted nessusd. A scan was run, and the output of this rule was in the style of the OLD version of the script - not the current! Hmmmm, so I did a "nessusd -R" , restarted - and no change. Similarly with a "killall -HUP nessusd" - still the old results show up. I finally renamed the file, changed the script_id number and ran it again - and still the old result shows up! Any ideas? Obviously something has got cached somewhere - but I can't figure out how the changed script_id didn't get noticed. This is with nessus-3.2.1 under CentOS4 -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
