[Openvas-discuss] OpenVAS not invoking nmap - how to fix?
nerdymark at gmail.com
Wed Aug 8 05:08:50 CEST 2012
I like to use nmap SVN, but I found OpenVAS 5 likes nmap 5.50. Run
openvas-check-setup and it might tell you about that. You will probably
have to find the source tarball and compile it because your package manager
probably doesn't have it.
Another thing I found with nmap, is that the default scan timeout is too
short if you're scanning a full range of ports on a remote host. Make a new
scan policy and adjust the default timeout to something like 2 hours if
that makes sense. Also, make sure nmap is enabled as a Port Scanner in your
policy. It might not be on as default, I don't remember.
To troubleshoot further, open a couple terminal windows, and tail -f
/var/log/openvas/*.messages and /var/log/openvas/*.dump. Run a scan and
maybe something helpful will show up.
On Tue, Aug 7, 2012 at 7:28 PM, Whit Blauvelt <whit at transpect.com> wrote:
> Putting this briefly for precision:
> What's required for OpenVAS to find and use nmap? I'm assuming the "Full
> fast" config in a default install should use nmap if available? But on both
> an Ubuntu 12.04 system with OpenVAS installed from recent sources, and a
> Fedora 15 system with OpenVAS installed from Atomicorp packages, despite
> nmap being on both systems, it's not used. Because it's not used, the
> OpenVAS report is basically null. Lots of processes get run without
> complaint, but the report is for practical purposes empty aside from the
> repeated list of all the ports it claims it probed, despite no report of
> finding the obvious stuff exposed on some of them.
> So where's the place to get OpenVAS to use nmap?
> And why doesn't it do it by default, if available, and complain if not?
> Openvas-discuss mailing list
> Openvas-discuss at wald.intevation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openvas-discuss