full-disclosure - Nessus experience

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <002d01c4b260$07c71a70$1600000a@spinoza>
From: samir at teknotrends.com (Samir Kelekar)
Subject: Nessus experience

----- Original Message ----- 
From: "Tate Hansen" <tate@...arNetSec.com>
>
> checks_read_timeout:  maximum number of seconds to wait for a probe
> response:  wait doing a recv()
> plugins_timeout:  the maximum number of seconds of lifetime for a
> vulnerability check
>
> If you set checks_read_timeout to 1 second and plugins_timeout to 5
seconds,
> you'll blaze through the scan.  The problem is you may lose accuracy
because
>
That is quite interesting.
Correct me if I am wrong, but it looks like
if the target interface that one is scanning is
blocked/down for some reasons, nessusd does not learn about it. (I guess it
might
be too much to expect). That is, every one of the plugins will get delayed
leading to
a huge time. Usually I haven't had the patience to wait for the whole scan
in such cases;
I guess it
could take days, am I right ?

regards,
Samir Kelekar
Teknotrends Software
Bangalore