Demo: Possible additional attacks detected in ECU manifest

[awwad]

Background

Secondary ECUs report, in their ECU Manifests, various data to the vehicle's Primary ECU and ultimately to the Director. This includes what is installed on the ECU, what the ECU's official clock reports (generally expected to be timeserver-validated), and what attacks have been detected by the Secondary ECU since its last ECU Manifest was sent.

Task

Review the demo Secondary code (demo_secondary.py) to determine if there are other meaningful reports that could be added to the attacks_detected element of the ECU manifest.

Consider also what can be gleaned from other code that may not currently be: are there things in the demo Primary that might come back to the demo Secondary that could be useful in attack reporting? More likely, are there things that happen in the reference implementation code for Secondaries (uptane/client/secondary.py) that could sensibly make it to the demo Secondary code and be reported?

You can search for attacks_detected in demo_secondary.py to find several examples of things being added to the attack reports.

[awwad]

Now that the attacks are in the demo, go through each attack and make sure that a reasonable attack string is added when each is recognized.