Monitor the device for reboot and take <appropriate> action

[Fuzion24]

if we crash the device, which does happen occassionally, we dont want to allow the user to continuously run VTS.

Maybe we can log the time when we run a scan. When another scan is requested by the user, we could check and see if the device was restarted shortly (a few seconds) after the scan was requested, or look for other clues indicating a device reboot.

If this is the case, we can notify the user that the vulnerability probe likely caused a device reboot and that they should consider their device vulnerable and to be weary of running the scan again.

[dweinstein]

maybe also consider disabling test temporarily that is believed to cause the crash. this might be handled if you keep a persistent log after each test and hope the crash doesn't lose filesystem writes

[Fuzion24]

jakevandyke:
what about if we just write a file. like user starts a scan, we write a file like "we_crashed". then perform all the tests and delete that file.
if the user starts our app and that file is there, then we know we broke something last time we performed a scan.
you could even do it on a per-test bases. write a flag before each test and then you'd know which one to not perform next time.