How to verify that a LOG file is legit?

[T-3B]

At the end of the LOGs file, there is always the hash Log FUN512: 1B9iFNr4ptOiMM_9hFpjMlme15QWCs6jD.orQGnqS2ZhhihrHsslZXJZ8o8tCWCdYGGsTIYV.F.uFhd4NfssUw.

Looking at cyanrip -h, I cannot find any option that can help to verify if any edit was made (e.g. any manual edit of the LOG file should result in a different hash FUN512 and there would be a mismatch with the one stored in the LOG).

How can I do it (if it is not possible at the moment, is this feature planned)?

[magicgoose]

Wouldn't it also require some sort of DRM / binary code obfuscation to implement?
In order to prevent someone from reusing this part of the code to re-sign any piece of text.