Iirc, years ago following was true (and I doubt it changed): Dependencies can mess the "Phases" up. If a ACT_SCANNER would depend on something from ACT_DENIAL, the ACT_DENIAL one would go first. The whole dependency-thing is indeed a hard (and interesting) problem to solve (but would be easy to detect).
--felix Am Donnerstag 13 September 2012 00:02:45 schrieb Thomas Reinke: > We're running into a hiccup with openvassd (rls 5) that I wouldn't > mind getting some feedback on. > > After upgrading both scanner and scripts, and removing find_service.nes > from the plugins directory so that there was no possibility of confusion > with find_service.nasl and the built in find_service plugin, a look at > the openvassd.messages log is showing that find_service.nasl is being > launched BEFORE nmap.nasl. > > My understanding is that nmap.nasl, with a category of ACT_SCANNER, > should ALWAYS execute before something like find_service.nasl, with > a category of ACT_GATHER_INFO. > > Is there something I'm missing? Shouldn't all ACT_SCANNER class > scripts be COMPLETELY finished, regardless of user config, before > other categories start firing up? This is preventing find_service.nasl > from working correctly. > > Thomas > _______________________________________________ > Openvas-devel mailing list > [email protected] > http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-devel _______________________________________________ Openvas-devel mailing list [email protected] http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-devel
