Andrew Blevins <[EMAIL PROTECTED]> writes: > I recently ran a few scans, and made sure I had the "safe checks" button > selected. Nessus ran the RFPoison check anyway.
That's odd, because "safe checks" should disable the ACT_DENIAL and ACT_DESTRUCTIVE_ATTACK plugins (launch_plugin function) > Does this safe check button override the unsafe checks if I have by > default all the plugins selected? It _should_. > Or does safe checks do something else? 1. "safe checks" makes the safe_checks functions returns "false". The script should test the result of this function. rfpoison.nasl does not call it, but... 2. "safe checks" disables the worst scripts. As rfpoison.nasl is an "ACT_DENIAL" script, it should not be run and you should find in your nessusd.messages file: Not launching rfpoison.nasl against xxx because safe checks are enabled (this is not an error) > Anyway, anyone have any answers to the "safe checks" question? Well, my nessus-core/doc/WARNING.En document was a little buggy. safe_checks is safer than what I thought. -- mailto:[EMAIL PROTECTED] GPG Public keys: http://michel.arboi.free.fr/pubkey.txt http://michel.arboi.free.fr/ http://arboi.da.ru/ FAQNOPI de fr.comp.securite : http://faqnopi.da.ru/
