Timeout/Watchdog for running Jobs

[gbena]

Being an automation tool, it is crucial to have a timeout/watchdog to prevent Jobs running endless and so preventing other Jobs to be executed.
Even when the security providers support timeout, it would be beneficial to have a native timeout supported directly in Hakbot. This way, we can have the same timeout defined for all provider. And can have a central place to set instead of going through all tools and set the timeout there. And timeout setting in Hakbot would even better when triggering security providers, which dont support timeout.

[stevespringett]

I could see this being defined on a per job basis. Some jobs may take a few days to complete whereas other jobs may take an hour or less. A global default per provider may work. 2 hours for Nessus and 24 hours for AppSpider. Burp, ZAP, and WebInspect, when complete, would also likely be 24 hours.