hi,
i would like to set a number of the nmap.nasl preferences ... notably
"Nmap (NASL wrapper)[checkbox]:Do not randomize the order in which ports
are scanned" => "yes",
and
"Nmap (NASL wrapper)[radio]:Timing policy" => "Insane",
i've been trying to do this using NessusWX, my own client written on top
of Net::Nessus::ScanLite, and my own hacked version of nessusc (Perl
client bundled with Net::Nessus::Client).
in each case, i set a packet sniffer going, launched my client ... and
then analyzed the resulting trace. and in each case, i can see the client
sending a PREFERENCES message which includes the above two preferences set
as i would them to be set ... but when nessusd actually launches its
attack, it doesn't honor either preference ... it randomizes the ports it
is scanning, and it uses a moderate timing policy ... i would guess
'Normal' from the packet rate i observe, but that's a guess.
has anyone else run into this? does nmap.nasl in fact not support
changing its parameters.
i've been poking through nmap.nasl itself ... i notice that the section
which reads the 'randomize' preference looks like this:
[...]
p = script_get_preference("Do not randomize the order in which ports
are scanned");
[...]
in particular, i notice that the word "order" has *two* spaces on either
side of it ... thinking this was significant, i modified my two Perl
clients to do the same ... but that didn't make any difference ... nessusd
still randomized the port scan and used a moderate timing policy.
insights appreciated
--sk
stuart kendrick
fhcrc
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
