MKB20_v77_Suzume_B35A.tgz submitted.
I tried the latest KEYDB.cfg and cannot rip the disk.
Please help to create the decryption key, thank you so much!
Dump Submitted - Suzume UHD HK Version
Re: Dump Submitted - Suzume UHD HK Version
The entry in the KEYDB.cfg file is probably this one, i.e. MKB20_v77_SUZUME_F26C.tgz. Have you emailed your TGZ file to svq@makemkv.com?
Re: Dump Submitted - Suzume UHD HK Version
Yes I emailed the B35A release dump, I guess it is different from the Korean version.MrPenguin wrote: ↑Sun Sep 08, 2024 6:54 pmThe entry in the KEYDB.cfg file is probably this one, i.e. MKB20_v77_SUZUME_F26C.tgz. Have you emailed your TGZ file to svq@makemkv.com?
Re: Dump Submitted - Suzume UHD HK Version
It may not be very different though. In fact, it might even use the exact same Unit Key as the Korean version, although the two disks will still obviously use different Volume Unique Keys (VUKs)...
.Re: Dump Submitted - Suzume UHD HK Version
How could I modify the cfg file to make the key applied to my disk?
I would like to try that.
Re: Dump Submitted - Suzume UHD HK Version
In theory, you could add an extra line to the KEYDB.cg file for your disk. See these instructions for how to calculate the disk's ID, i.e. the SHA1 hash of the AACS\Unit_Key_RO.inf file. However, in actual practice, MakeMKV still needs to know the disk's VUK unless you also install third party decryption software such as Xreveal which only needs the Unit Keys.
Re: Dump Submitted - Suzume UHD HK Version
If you fetch the latest keydb MKB20_v77_Suzume_B35A should now work with MakeMKV