I'm scanning a very fragile host, and I need to be able to figure out which plugins out of a couple thousand are causing the host to crash, so I've written a script that creates a config with a single plugin selected, creates the task, and runs the scan, then checks the results and runs a simple test to make sure the host is still alive before continuing with the next plugin. If it detects that the host has died, then my script restarts the host to continue scanning, logging which plugin caused the host to crash.
However, for a script like this to work well, I need to be able to have the knowledge base created after each test to be saved and then loaded by the next test, but it isn't working. Despite that the configs are set to save/restore the KB, and the max age is set to 24 hours, the KB simply isn't being saved or loaded. I tested this by creating a plugin that simply dumps the contents of the KB. When I create a config with a port scan and my KB dumping plugin, then I see the port scan results in the KB. If I immediately run another task with just the KB dump, I don't see the port scan results. I would expect that the first task would have saved the port scan results to the KB and the second task would read that saved KB and dump it. I'm running CentOS 6, OpenVas Manager 5.0.5, Scanner 4.0.5, and GSAD 5.0.4. The strange thing is that on another system, I'm running an older version of OpenVAS (Scanner 3.3.1, Manager 3.0.6, Admin 1.2.1, GSAD 3.0.3) and it works fine, but I can't scan my fragile host from that system due to the network setup. On that system, I can see the KBs being saved in /var/lib/openvas/users/om/kbs, but on my system running the newer OpenVas, the files there aren't being created. Is there perhaps something I'm missing?
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
