Hello NVT developers; I have just committed a major change in the way openvassd manages its knowledge base (CR-62). It should have no impact on the way NVTs behave but it can also help you developing new NVTs or debugging suspicious ones.
Once redis is started, you can issue the following command to see everything that happens during the execution. # redis-cli -s <path to the redis server socket> MONITOR The default path is /tmp/redis.sock. Then start the scan or openvas-nasl. You should be able to follow precisely the interactions between the scanner and the KB server. http://redis.io/commands/MONITOR Regards -- Henri _______________________________________________ Openvas-plugins mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-plugins
