I have difficulties to understand your answer. When are the Nmap Nasl Wrapper settings coma into action and when the Launch Nmap for Network Scanning settings? According to your answer means we should disable Nmap plugins and Nmap portscanner? Or is it disabled by default? For example the deep and ultimate config has the Nmap port scanner activated. I'm now confused.
-----Ursprüngliche Nachricht----- Von: Openvas-discuss [mailto:[email protected]] Im Auftrag von Jan-Oliver Wagner Gesendet: Dienstag, 2. April 2013 16:57 An: [email protected] Betreff: Re: [Openvas-discuss] Difference between Nmap Nasl Wrapper and Launch Nmap for Network Scanning settings On Dienstag, 2. April 2013, Allon Moritz wrote: > As the title says what is the difference between the "Nmap nasl > wrapper settings" and the "Launch Nmap for Network Scanning" settings. > For what are they used as they look pretty much the same? Thanks. the core idea is to take advantage of Nmap's ability to scan multiple hosts concurrently in a network scanning phase. As suggested by the Nmap developers that launching nmap for each single host is suboptimal. It is not too well tested, thats why it was not made default yet. Currently I hesitate a bit to work further on this as there are some licensing conditions I'd like to fully understand and comply with first, see my questions on nmap-dev. Best Jan -- Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/ Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 202460 Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
