[Openvas-discuss] OpenVAS still has its own port discovery service? And which is the right switch to add nmap?

Whit Blauvelt whit at transpect.com
Thu Aug 9 17:26:19 CEST 2012

On Thu, Aug 09, 2012 at 05:21:24PM +0100, Matthew Mundell wrote:
> > Now, I'm guessing since others report scans finding ports when run with the
> > default config that "Nmap (NASL wrapper)" must be effective for them and not
> > for me? I also see that using Nmap with an NASL wrapper is the way Nessus
> > handles it. What an NASL wrapper is I don't know. But this sure looks like
> A NASL wrapper is an NVT (an OpenVAS script) that calls the nmap command.

Okay, so that's not working for me. On two quite different systems/installs. 

> > where the breakage has been for me. Something else I'd need to install to
> > have this work? Or does "Nmap (NASL wrapper)" being on mean nothing without
> > "Launch Nmap for Network Scanning" also being on? That is, are they
> > alternate ways of running Nmap, or interdependent? Per the Nessus docs,
> They are alternate ways.

Okay, turned "Launch Nmap for Network Scanning" on and "Nmap (NASL wrapper)"
off, pointed it to a single IP with known services exposed, and it still
finds none of them.


More information about the Openvas-discuss mailing list