This feature would allow modules to register hooks for certain event types, so when those events were emitted, they would be the first to receive them. They could do their own tagging/tweaking of the event, then release them to the scan.
This would be ideal for tasks like tagging web screenshots as "old" or "parked", etc. It may also be an ideal place for our current DNS resolution system; where our DNS logic would become an internal module that registers a hook for IP_ADDRESS and DNS_NAME.
This would result in a lot of code cleanup, as we could move the complex dns resolution logic and cloudcheck tagging etc. into their own internal modules -- dnsresolve, cloudcheck, etc.
@liquidsec
This feature would allow modules to register hooks for certain event types, so when those events were emitted, they would be the first to receive them. They could do their own tagging/tweaking of the event, then release them to the scan.
This would be ideal for tasks like tagging web screenshots as "old" or "parked", etc. It may also be an ideal place for our current DNS resolution system; where our DNS logic would become an internal module that registers a hook for IP_ADDRESS and DNS_NAME.
This would result in a lot of code cleanup, as we could move the complex dns resolution logic and cloudcheck tagging etc. into their own internal modules --
dnsresolve,cloudcheck, etc.@liquidsec