Nessus nmap.nasl

Some concerns with the nmap.nasl's scanning mechanisms, efficiencies,
and abilities after reading the following statement from Michel Arboi: 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Nmap can crash broken IP stacks. --- The latest versions of the
nmap.nasl wrapper disable those dangerous options (OS fingerprinting,
TCP stealth scans, UDP scan, aggressive timings) --- [When using
safe_checks()]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

As a suggestion: perhaps the following nmap.nasl plugin preference
should be implemented in order to bypass the default safe_checks()
allowing the use of other common scanning techniques and timings.


Line 48:

script_add_preference(name:"Run Plugin as Safe_Plugin", type:"checkbox",
value: "yes");


....


line 131

safe = script_get_preference("Run Plugin as Safe_Plugin :")
if (safe == yes)
{ 
 safe = safe_checks();
}

....

Matthew Lalumiere

Verisign
www.verisign.com
------------------
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus