[Openvas-discuss] OpenVAS still has its own port discovery service? And which is the right switch to add nmap?
matthew.mundell at greenbone.net
Thu Aug 9 18:21:24 CEST 2012
> 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.
> 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.
> there Nmap _requires_ the NASL wrapper. But of course the configuration
> method is quite different.
> As side question, GSA _only_ allows scan configs to be base on "Full and fast" or
> an empty config. Or I suppose other configs can be exported to XML and then
> imported and edited? But why not take the same direct route to modification?
We started with just "Empty" and "Full and fast" in the interface. In the
protocol it is possible to base it on any config. The demand for this has
been low, I guess.
Greenbone Networks GmbH
Neuer Graben 17, 49074 Osnabrueck, Germany | AG Osnabrueck, HR B 202460
Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner
More information about the Openvas-discuss