Closed
Description
Problem
Occasionally, some hosts fail to report the scan results despite that ssh connectivity checks and sudo checks pass. In such cases, Vuls stops abruptly, discarding the rest of the results.
I need an option to continue to produce the scan results even if it loses contact with part of the designated hosts during scan.
Suggested procedures
- Add
-ignore-failures
option so that Vuls tries to finish the whole scanning process even when some hosts act up mid-scan. - Define Scan failed JSON data to show in the TUI, send to Slack, etc.
P.S.
While I was investigating this problem, I found another thing-- When a host is loaded with vulnerabilities, -report-slack
may fail because Slack declines messages with too may attachments. I'll raise a separate issue regarding this.