a01ik3d4_1018 wrote: Fri Dec 19, 2025 3:42 am
Here I'm posting a shared link to the dump file for the Blu-ray disc I want Keydb to support. It's probably something no one has shared yet.
Thanks for the submission. Both of your discs have been added to the public keydb.
a01ik3d4_1018 wrote: Fri Dec 19, 2025 3:42 am
Also, could someone please tell me how to check if my disc's ID is already entered in Keydb
You can check the current support status by calculating the SHA-1 hash of the
Unit_Key_RO.inf file within the AACS directory on each disc. Once you have this hash, you can open up the extracted keydb.cfg file in any text editor and search for the disc ID value.
As an example, the disc ID of your first disc is 0xECB4A28B5FA283600812C1D416325AC483778993. If you search for this hash in the keydb you'll see a line like this:
Code: Select all
0xECB4A28B5FA283600812C1D416325AC483778993 = ACEes Arena Tour 2025 PROLOGUE DISC1 | D | 0000-00-00 | M | 0x77<Redacted for the forum> | I | 0xD5<Redacted for the forum> | V | 0xCD<Redacted for the forum> | U | 1-0xA2<Redacted for the forum> ; MKBv82 (BD)
a01ik3d4_1018 wrote: Fri Dec 19, 2025 3:42 am
where disc IDs are added in the first place—is it the public key database?
Disc
IDs are trivial to calculate and don't actually facilitate decryption. Decryption requires disc
keys, and I do believe the public keydb is the fastest option for disc keys these days.
The following UHD discs have also been added to the public keydb:
Code: Select all
MKB20_v77_OSAKAMONO_UHD_442C
MKB20_v82_SPACE_1999_BREAKAWAY_9F6E
mkb20_v82_uhd_shine_242b