Xreveal 2.9.2.7 beta released
2026-04-13Changelog Version 2.9.2.7 2026-04-13 Replaced the image checksum algorithm from MD5 to the fast SHA-1 Improved support for verifying content hash of the decrypted MakeMKV backup #1127
Replaced the image checksum algorithm from MD5 to the fast SHA-1
When the ‘Create image checksum file' is checked, Xreveal will calculate SHA-1 of the destination image file, and create file
PRINCESS MONONOKE.iso
PRINCESS MONONOKE.sha1
27c0c2d33178f165b10a8a08a92354c94fa5cca5 *PRINCESS MONONOKE.iso
On macOS and Linux or WSL, you can use sha1sum -c 'PRINCESS MONONOKE.sha1' to verify the checksum.
Improved support for verifying content hash of the decrypted MakeMKV backup #1127
Recently trying Xreveal and bought a pro license. I already have several backups made with MakeMKV. When I run the hash checker on some of the backups, I get fails. This seems to be because keydb.cfg does not have an entry for the discs. If I open the actual disc with xreveal, the key is added to My Discs and the hash check will then succeed. I see in https://www.xreveal.com/news?id=145 that it seems only the keydb is used by xreveal. Is it it possible to have the program read the key from the MAKEMKV dir in the backup so the hash check will succeed? Or is there there a way to import keys from MakeMKV program (user\.MakeMKV is where they are stored?)? I see the Keydb Helper is often recommended, but does this get keys from MakeMKV too? It sounds to me like it only gets the public keydb for MakeMKV to use, which isn't helpful right now since it doesn't seem to have entries for some of my discs. zep* 2026-04-13
<MakeMKV-Decrypted-Backup-Folder>\MAKEMKV\discattd.dat contains VID, which could calculate derivative unit keys for the regular Blu-rays.
For UHDs, because there is no valid PK to calculate derivative unit keys, this process won't work.
We're not sure if MakeMKV will obfuscate the VID in discatt.dat or discattd.dat. If the VID is obfuscated, this process won't work.