On Mittwoch, 23. Juli 2014, Thomas Reinke wrote: > >> Probably would be good to understand and handle the logic in the nasl > >> scripts that still rely on the "default" values... > > > > hm, which ones are these? > > nmap.nasl, amap.nasl, portbunny.nasl, portscan-strobe.nasl, pnscan.nasl > > In short, after you dig through code, it seems with a setting of > default, invoking scanner_get_ports eventually finds it's way to > the "getpts" function call, to get_tcp_svcs, which reads the > openvas file /usr/local/var/lib/openvas/services.tcp, specifically > to be able to get a list of ports.
According to openvas-libraries/ChangeLog, on 2013-03-01 the handling of this file was removed. Same day the "default" was removed. It was me who removed it and I remember this code part was a nightmare. > So there's still a whole bunch of infrastructure, afaik, that is > designed to support the concept of a 'default' scan, which would > appear to be controlled by what is defined in these files. On the Feed side the support of "default" was kept in order to support OpenVAS-5 installations (but not for a long time anymore). -- 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
