minor: runtime_data: declared checksums structure

[SmileyAG]

This request does NOT solve the issue, but simply gives it a some start in resolving.

Hashes will be transmitted as strings instead of the hardcoded amount of allocated bytes for them, just so that if something happens we can easily change the hashing algorithm without consequences for this.

On the parser side, we can always check whether the string contains any other characters other than a-F and 0-9 as validity (basically to make sure that this string corresponds to hexadecimal format)

And a simple way on the parser side to determine the type of algorithm is by the number of characters (e.g. MD5 is 128 bit = 128 / 8 = 16 * 2 = 32 characters); this is could be used for comparison with some hardcoded list of hashes in parser side

We also need to return at least the logging name of the server module later, since modules logging was removed with this commit: 1d049ef

I also don’t see much point in logging the names of all loaded modules, but the name of the server module (hl.dll and etc) must be logged for the purpose to working with hardcoded list of hashes (e.g. since list might be formatted in way like: "server_module_name", "md5_hash", "sha1_hash", "sha256_hash")

[YaLTeR]

Maybe instead a map from name to checksum? Then it can have "hl.dll" => checksum, "client.dll" => checksum, and whatever else we may add in the future?

[SmileyAG]

Oh, that's a really good idea in fact. After all, maybe in the future this field with all the loaded modules will still be needed again, who knows, so it's better not to re-use it again just for this.