Is there any guidance on how the MD5 of the various files is used in scenarios? I'm fully aware of what and MD5 is; it just seems that the implementation of it here isn't standard and I'm trying to puzzle it out. Take for example a simple example scenario: ScenarioProperties.xml contains an MD5 XML tag of B657F8F034FDF9009D8CAB84B0B8FDE2. However, the MD5 hash of that file is actually 2F0BEDCF040F74BFD18E69F071C42CD1. Additionally, no other file in the scenario folder has a MD5 hash that matches the XML tag, including a conversion of ScenarioProperties.xml to ScenarioProperties.bin. Additionally, there's ScenarioProperties.xml.MD5. Reading that binary file as hex gives us a value of DE26895DB721A22B6C4F47B9A692221C. Once again, not only does this not match the MD5 hash of ScenarioProperties.xml, but it matches neither any other scenario file nor the MD5 in the XML tag. Which raises the obvious question: Where are the hashes coming from? They seem completely disconnected from the files used to drive scenarios instead of being used to verify file integrity.
