Minecraft instance is not hashing the server.jar properly

OS Name/Version: Raspberry Pi OS Lite 64bit based on Debian version: 11 (bullseye)

Product Name/Version: AMP Release “Triton” v2.3.2.8, built 28/03/2022 15:34

Problem Description:
For security, I have setup my Minecraft instance to only run hash approved server.jar files. But the server won’t start because the hash is not in the list.

MD5 hash generated with AMP file manager and the above mentioned OS, plus Linux Mint:
The MD5 Hash the logs are seeing:
Hash for ./Minecraft/fabric_server.jar: 2746b37d0a83c56e3d69160bca67d26f

Using the hash from the logs, allows me to start the server, but I don’t understand why the same file has 2 MD5 hashes. Is this a bug?

No it’s not a bug. It’s not a standard MD5 hash. The hash has to be generated by AMP.

Ok that makes sense. But how do you get the hash without digging into lvl 0 logs?

That is why I used the file manager MD5 option, expecting it to be the official way of hashing the file.

Via the Level 0 logs. It wasn’t really a feature intended to be used by regular users.